Re: UDP Sockets & Clock Synchronization
Re: UDP Sockets & Clock Synchronization
- Subject: Re: UDP Sockets & Clock Synchronization
- From: Vincent Lubet <email@hidden>
- Date: Tue, 26 Feb 2002 09:23:01 -0800
Can't you just block your thread on recv() instead of using select()?
Vincent
On Monday, February 25, 2002, at 09:44 PM, Zack Morris wrote:
Hi, I am messing with sockets on OS X and I need a way to have an
"interrupt" that fires when a UDP packet comes in. Using select()
doesn't
really help, because if my game runs at 30 fps, that means I have a 33ms
uncertainty about when a packet came in (if I poll the network each time
through my main loop). I need something similar to the asynch mode of
OS 9.
That's because I send out a "ping" packet (using UDP) with the current
time.
Ont the other end, the server needs to see the packet come in and
return a
response packet as quickly as possible to mimimize the latency. The
original computer gets that response packet and looks at the server's
time
and round trip time to compute how much to change the clock by.
Obviously
throwing an extra 33ms in there doesn't help! Is there a way to do
this?
P.S. It would be nice if this worked with GUSI so I could have one
method,
but it's not mandatory...thanx for your time,
Zack Morris
Z Sculpt Entertainment
email@hidden
http://www.zsculpt.com
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.