Re: Need sleuth for UDP blues.
Re: Need sleuth for UDP blues.
- Subject: Re: Need sleuth for UDP blues.
- From: Graham Parkinson-Morgan <email@hidden>
- Date: Wed, 24 Mar 2004 21:21:01 -0800
Erk. Seems that replying goes to Matt rather than back to the list.
On receiving a T_DATA event, you need to keep calling OTRcvUData()
until it returns a kOTNoDataErr. You can also use OTCountDataBytes()
to check if there is any outstanding data.
That was the glaringly obvious point that I missed. I went back to the
documentation and there is that line at the end of the explanation of
OTRcvUData, plain as the snout on my face, and I must have read that
paragraph about 4 times today, so many thanks!
On OSX the OTNotifyProc tops and tails itself with an OTEnterNotifier/
OTLeaveNotifier critical section in case that is important).
That's unnecessary. Those calls are used when you want protected access
to a data structure that's also touched by the notifier. They block any
calls to the OT notifier until you release the synchronization
primitive.
And out they go. Thanks once more.
Good to find this list.
_______________________________________________
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.