Re: Need sleuth for UDP blues.
Re: Need sleuth for UDP blues.
- Subject: Re: Need sleuth for UDP blues.
- From: "Matt Slot" <email@hidden>
- Date: Wed, 24 Mar 2004 22:45:33 -0500
Wed, 24 Mar 2004 16:52:37 -0800
>
OTRcvUData is successful; flags return
>
0, and the callback completes. But OT appears to get stuck with the
>
next packet (just guessing). Even if I go back to broadcasting just one
>
packet at a time from the PC, Mac B's OTNotifyProc never gets called
>
again. No crash. No instability. Nothing.
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.
>
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.
Matt
+--------------------------+-----------------------------------+
| Matt Slot | Ambrosia Software, Inc. |
| Bitwise Operator |
http://www.AmbrosiaSW.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.