Re: T_MEMORYRELEASED
Re: T_MEMORYRELEASED
- Subject: Re: T_MEMORYRELEASED
- From: Jens Bauer <email@hidden>
- Date: Fri, 22 Feb 2002 23:10:55 +0100
Hi Scott,
On Fri, 22 Feb, 2002, Scott Burgess <email@hidden> wrote:
{snip}
>
The notifier is loosely:
>
>
AsyncNotifier()
>
{
>
OTEnterNotifier()
>
>
switch ( code )
>
{
>
case T_MEMORYRELEASED:
>
break;
>
>
}
>
>
OTExitNotifier()
>
}
I'm not sure that you should call OTEnterNotifier and OTLeaveNotifier
from within the notifier function itself. It's usually used to shield
against notifier calls.
I believe that the above *could* cause unwanted results, such as your
notifier being called while you're already inside it (after you call
OTLeaveNotifier).
You will also only block one endpoint's notifier from executing, not all
of them.
I do not know if this could affect the T_MEMORYRELEASED event, as I do
not know the internal workings of Open Transport, just some of the basics.
(I assume you already have a copy of the OTVirtualServer sample code,
which shows an example of handling the T_MEMORYRELEASED event.
Unfortunately it doesn't give examples on handling flow-control, but you
may be able to substitute this yourself, which reminds me that I ought to
give it a try. ;))
Love,
Jens
--
Jens Bauer, Faster Software.
-Let's make the World better, shall we ?
_______________________________________________
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.