[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #28605] Write can block when cable unplugged
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #28605] Write can block when cable unplugged |
Date: |
Thu, 14 Jan 2010 20:14:25 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 |
Follow-up Comment #1, bug #28605 (project lwip):
Could you go a bit more in detail why calling the API_EVENT in that case
helps? I would have thought we might want to abort the write with 'failed' in
this case, but that's kind of risky when part of the data has already been
sent...
And what do you mean by 'make the socket_select() a little less bumpy '?
Oh, and when giving line numbers, it's always a good idea to include the
version of the file, as currently, line 1015 is a comment line... :-)
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?28605>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #28605] Write can block when cable unplugged, Fabian Koch, 2010/01/14
- [lwip-devel] [bug #28605] Write can block when cable unplugged,
Simon Goldschmidt <=
- [lwip-devel] [bug #28605] Write can block when cable unplugged, Fabian Koch, 2010/01/15
- [lwip-devel] [bug #28605] Write can block when cable unplugged, Fabian Koch, 2010/01/15
- [lwip-devel] [bug #28605] Write can block when cable unplugged, Simon Goldschmidt, 2010/01/15
- [lwip-devel] [bug #28605] Write can block when cable unplugged, Simon Goldschmidt, 2010/01/23
- [lwip-devel] [bug #28605] Write can block when cable unplugged, Simon Goldschmidt, 2010/01/23
- [lwip-devel] [bug #28605] Write can block when cable unplugged, Simon Goldschmidt, 2010/01/27
- [lwip-devel] [bug #28605] Write can block when cable unplugged, Simon Goldschmidt, 2010/01/27