Message91299
| Author |
gpolo |
| Recipients |
ajaksu2, dhanlen, ggenellina, gpolo |
| Date |
2009年08月05日.02:48:26 |
| SpamBayes Score |
6.062668e-06 |
| Marked as misclassified |
No |
| Message-id |
<ac2200130908041948s64ecd1d5i2758aca0d03647@mail.gmail.com> |
| In-reply-to |
<1249436858.75.0.0680769178287.issue2710@psf.upfronthosting.co.za> |
| Content |
> AFAIK, WSAEWOULDBLOCK means that the socket is in nonblocking mode and
> the attempted operation could wait indefinitely to complete.
Rather pessimistic way to see it :) I've always read it as "operation
cannot be completed without blocking".
> But I
> don't understand how that could happen since a previous select()
> confirmed the socket is writeable...
Richard Stevens, MSDN
(http://msdn.microsoft.com/en-us/library/ms741540(VS.85).aspx) and
possibly several other authors and places will tell it is possible to
happen. I've always seen this being handled as "try again later". |
|