Re: More on detecting dropped connections
Re: More on detecting dropped connections
- Subject: Re: More on detecting dropped connections
- From: Vincent Lubet <email@hidden>
- Date: Mon, 15 Apr 2002 09:18:21 -0700
On Monday, April 15, 2002, at 08:56 AM, Tom Bayley wrote:
Thanks for that Vincent. One comment I have though on the following:
On Monday, April 15, 2002, at 04:41 PM, Vincent Lubet wrote:
You can fetch and clear the error by calling getsockopt() for the
option SO_ERROR, or alternatively, a read() or a write() will fail and
set errno to the error code.
I don't know about read(), but I have found that recv() does not return
an error in this case under OS X. That was the source of our problem.
This is very weird because both system calls read() and recv() end up
calling the same socket receive routine that checks the socket error
condition.
Could you please file a problem report with detailed steps on how to
reproduce the problem (source code would be ideal).
Thanks,
Vincent
_______________________________________________
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.