Twas brillig at 14:35:29 20.09.2009 UTC+02 when [email protected] did gyre and gimble:
HS> Assume two TCP connections were served simultaneously, how could a HS> process call read() or recv() on the socket descriptor without the HS> risk of being blocked? Erm. Make it non-blocking? :) Actually, select() specification makes non-blocking sockets nearly useless. Why do they exist at all? Just as a convenient shortcut for "select with 0s timeout + read/write"? -- http://fossarchy.blogspot.com/
pgpnf2ZYbZJJD.pgp
Description: PGP signature
_______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
