Hello > This would be a valid argument if the standard didn't specifically > provide > us a way to get the exact guarantee you want. It's this simple: > > 1) You need a particular guarantee, specifically, that a 'read' won't > block. > > 2) The standard provides you a clear way to get that guarantee, by > setting > the socket non-blocking. > > 3) You can't think of any way for the 'read' to block, but you are not > guaranteed it. > > How hard is that to follow? If we are talking about standards, maybe you should read new releases of documents which you are citing as an authority. From 1997 to 2004 many things changed: http://www.opengroup.org/onlinepubs/009695399/functions/select.html
For short: A descriptor shall be considered ready for reading when a call to an input function with O_NONBLOCK clear would not block, whether or not the function would transfer data successfully. (The function might return data, an end-of-file indication, or an error other than one indicating that it is blocked, and in each of these cases the descriptor shall be considered ready for reading.) How hard is that to read new releases ? Best regards, -- Marek Marcola <[EMAIL PROTECTED]> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
