[Python-Dev] noreply@sourceforge.net: [Python-bugs-list] [Bug #111620] lots of use of send() without verifyi ng amount of d (original) (raw)
Greg Ewing greg@cosc.canterbury.ac.nz
Mon, 14 Aug 2000 16:24:43 +1200 (NZST)
- Previous message: [Python-Dev] noreply@sourceforge.net: [Python-bugs-list] [Bug #111620] lots of use of send() without verifyi ng amount of d
- Next message: [Python-Dev] noreply@sourceforge.net: [Python-bugs-list] [Bug #111620] lots of use of send() without verifyi ng amount of d
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Fredrik Lundh <effbot@telia.com>:
fwiw, I still haven't found a single reference (SUSv2 spec, man- pages, Stevens, the original BSD papers) that says that a blocking socket may do anything but sending all the data, or fail.
The Solaris manpage sort of seems to indirectly suggest that it might conceivabley be possible:
EMSGSIZE The socket requires that message be sent atomi-
cally, and the message was too long.
Which suggests that some types of socket may not require the message to be sent atomically. (TCP/IP, for example.)
Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg@cosc.canterbury.ac.nz +--------------------------------------+
- Previous message: [Python-Dev] noreply@sourceforge.net: [Python-bugs-list] [Bug #111620] lots of use of send() without verifyi ng amount of d
- Next message: [Python-Dev] noreply@sourceforge.net: [Python-bugs-list] [Bug #111620] lots of use of send() without verifyi ng amount of d
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]