[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #28968] some request & DNS bug
From: |
David Empson |
Subject: |
[lwip-devel] [bug #28968] some request & DNS bug |
Date: |
Mon, 22 Feb 2010 23:16:15 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 |
Follow-up Comment #4, bug #28968 (project lwip):
Mac OS X (derived from BSD Unix, and certified as standard Unix) appears to
be the same as Linux.
If you use setsockopt() to enable SO_RCVTIMEO, and insufficient data is
received, then recv() will return after the timeout period. If no data was
received, recv() returns -1 and errno is set to EAGAIN (EWOULDBLOCK is
#defined as EAGAIN). If some data was received (but not enough to satisfy the
length parameter) then a reduced count is returned but no error is reported.
The ETIMEDOUT error means that the connection has timed out (hence is
unusable), so it is a fatal error.
Regarding the Windows API: in a somewhat old copy of MSDN, I can't see
mention of any mechanism for a timeout on recv(), and there is no SO_RCVTIMEO,
so Windows doesn't have a defined error code for that situation (unless one
has been added since 2001).
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?28968>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/