Re: InitOpentransportInContext
Re: InitOpentransportInContext
- Subject: Re: InitOpentransportInContext
- From: Quinn <email@hidden>
- Date: Tue, 25 Feb 2003 17:35:29 +0000
At 14:04 -0500 24/2/03, Alice Hartley wrote:
Can you quantify "especially". It certainly used to be necessary.
On traditional Mac OS, putting the machine to sleep will typically
close all of the TCP/IP endpoints. You would be notified of this via
the kOTProviderWillClose/kOTProviderIsClosed events. This affects
all TCP/IP endpoints, regardless of their state.
I say "typically" because under certain circumstances (for example,
later Mac OS 9 systems on ARPable links and those machines that
support wake on LAN when they're using Ethernet) this doesn't happen.
On Mac OS X, putting the machine to sleep has no direct effect on
your endpoints. However, if the machine wakes up and can't confirm
its original IP address, the IP address of the machine might change
and this will make any endpoint that is bound to that source address
stale (it still exists, it just can't talk to anyone).
DTS Technote 1145 "Living in a Dynamic TCP/IP Environment" explains
this situation in much greater detail.
<
http://developer.apple.com/technotes/tn/tn1145.html>
The above only covers endpoints. AFAIK there is no version of Mac OS
that requires you to reconnect to *Open Transport* on sleep/wake.
Thus, you shouldn't need to call
InitOpentransportInContext/CloseOpenTransportInContext on sleep/wake.
S+E
--
Quinn "The Eskimo!" <
http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
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.