site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Thread-index: AcdmjaNU4ho1uNKAEduhfAAWy4i6sA== Thread-topic: TCP/UDP sockets and hardware sleep User-agent: Microsoft-Entourage/11.3.3.061214 I'm having trouble determining the best way to handle IP sockets when a Mac goes to sleep. Here is a very simple example: 0) Ethernet is connected to a wired network. Airport is turned on and has selected an access point. 1) connect a socket to a different computer - connection is made via built-in Ethernet 2) Notebook computer is put to sleep by closing the cover 3) Ethernet cable is removed 4) Computer wakes up (lid opened), joins a different wireless access point attached to a different network. 5) Software sends data on the connected socket. 6) Software performs a read on the socket Does a standard TCP/IP timeout cause the read call to fail? Is this guarranteed to happen? I'm observing that the read might not return. Paul Nelson Thursby Software Systems, Inc. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com