TCP/UDP sockets and hardware sleep
TCP/UDP sockets and hardware sleep
- Subject: TCP/UDP sockets and hardware sleep
- From: Paul Nelson <email@hidden>
- Date: Wed, 14 Mar 2007 18:08:12 -0500
- Thread-topic: TCP/UDP sockets and hardware sleep
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden