Re: OTNotifier in shared libraries
Re: OTNotifier in shared libraries
- Subject: Re: OTNotifier in shared libraries
- From: "Duane Murphy" <email@hidden>
- Date: Fri, 24 Jan 2003 12:07:23 -0800
--- At Fri, 24 Jan 2003 08:21:49 -0800, Roy Lovejoy wrote:
>
I would appreciate any input on this matter:
>
>
We have a suite of shared libraries (plug-ins to a host app), and we are
>
trying
>
to communicate between them via asynchronous UDP endpoints & OTNotifier
procs.
>
>
Things just "aren't happening". Timing seems to be counter intuitive.
>
>
Wrapping the OTSndUData() with DCon dprintf's, and putting dprintfs in the
>
OTNotifier, I would have expected a trace like:
>
>
Before OTSndUData()
>
Inside OTNotifier() - got T_DATA
>
After OTSndUData()
>
>
but I don't.. sometimes the "Inside OTNotifier()" is after many other OT
calls
>
and in our case, too darn late.
>
>
If the receiving endpoint is asynchronous, and it has the OTNotifier, why the
>
delay?
>
>
This is in a Classic host-- does the OTNotifier do it's business within WNE??
I cant speak of the implementation, but I can from experience. OT does
everything at what is essentially WNE time. There is no preemption. If
you dont give the system time via WNE then nothing much actually happens.
I would expect this to be doubly true of asynch communication. This seems
counter intuitive until you consider the implementation. Asynch just
places the request in a queue and the queue gets serviced "some other
time." That "other time" is when WNE is called by you or anyone else.
I hope at least some of this is helpful. I would really like to know if
this conclusion is incorrect. As I say, this is from experience.
...Duane
_______________________________________________
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.