Unbinding an endpoint in OT when running in Classic.
Unbinding an endpoint in OT when running in Classic.
- Subject: Unbinding an endpoint in OT when running in Classic.
- From: Graham Parkinson-Morgan <email@hidden>
- Date: Tue, 13 Apr 2004 12:41:52 -0700
I find that if I listen on a port in a PPC app running in Classic, I
can unbind the endpoint, close OT, shut down the app, fire the app once
more, rebind to the same port and listen as many times as I like.
However, if I then run a Carbon version of the same application on OSX,
immediately after shutting down the PPC version running in Classic, OT
tells me the port in question is still in use, and I find that I have
to shut down Classic before the port becomes available once more.
The sequence used to shut down the asynchronous endpoint is:
OTSetSynchronous
OTUnbind
OTRemoveNotifier
OTCloseProvider
The error returns for this sequence are logged. Not a peep.
In any event, I would have thought that shutting down the application
would have been enough for the process manager inside Classic to tear
down any hold OT had on a port.
My question is, would there be anything else I can do to ensure that
Classic has relinquished control over this target port?
Graham.
_______________________________________________
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.