Author xdegaye
Recipients Nidan, giampaolo.rodola, josiahcarlson, python-dev, stutzbach, xdegaye
Date 2013-05-10.08:35:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368174928.38.0.027262086241.issue16133@psf.upfronthosting.co.za>
In-reply-to
Content
For the reson why read() must still check for EWOULDBLOCK even though
after select() has reported a file descriptor ready for reading, see
the BUGS section of select linux man page, which says:

       Under Linux, select() may report a socket file descriptor as
       "ready for reading", while nevertheless a subsequent read
       blocks.  This could for  example  happen  when data has arrived
       but upon examination has wrong checksum and is discarded.
       There may be other circumstances in which a file descriptor is
       spuriously reported as ready.  Thus it may be safer to use
       O_NONBLOCK on sockets that should not block.
History
Date User Action Args
2013-05-10 08:35:28xdegayesetrecipients: + xdegaye, josiahcarlson, giampaolo.rodola, stutzbach, python-dev, Nidan
2013-05-10 08:35:28xdegayesetmessageid: <1368174928.38.0.027262086241.issue16133@psf.upfronthosting.co.za>
2013-05-10 08:35:28xdegayelinkissue16133 messages
2013-05-10 08:35:27xdegayecreate