Re: T_MEMORYRELEASED
Re: T_MEMORYRELEASED
- Subject: Re: T_MEMORYRELEASED
- From: "Scott Burgess" <email@hidden>
- Date: Fri, 22 Feb 2002 13:46:29 -0800
Might have figure it out. When handling the
T_MEMORYRELEASED event, the code went on
to call OTSnd several times from within the
notifier, which I guess causes problems.
Scott
Assuming I have an endpoint that is:
a) non-blocking
b) ack-ing sends
c) asynchronous
is there any circumstance under which
T_MEMORYRELEASED won't be received after
an OTSnd() call?
The notifier is loosely:
AsyncNotifier()
{
OTEnterNotifier()
switch ( code )
{
case T_MEMORYRELEASED:
break;
}
OTExitNotifier()
}
Is there any chance that T_MEMORYRELEASED
gets lost if the notifier is called before
the OTSnd() completes?
This seems to be happening with OS 8.1/OT 1.3.1.
I don't seem to have the problem with OS 9.2.2/
OT 2.7.9.
Thanks a huge amount
Scott Burgess
_______________________________________________
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.