[Spread-users] Is there a limit on total traffic sent by Spread?

[Tim Peters]

[Me]
> Not quite:  the loop is happy if it gets even one byte, regardless of how
> many it expects (then it records as much as it saw, and returns).  In any
> case, there's no select() guarding the recv() calls in the loop, so no
> reason to consider EWOULDBLOCK exceptional for them.

BTW, I should make clear that the unexpected disconnection deaths we've seen
in Sess_Read under heavy load were all due to the recv() call inside the
loop (it sometimes returns -1 and sets errno to EWOULDBLOCK (== EAGAIN)).