Understood on change in state between writable event firing and socket could close by the time you goto write. In which case the read event would fire next and result in zero bytes read signaling the socket is closed.
Your statement below is exactly what I have dealt with on many systems. Resulting in TCP buffer overflow and RAM bloat/leak. "One possible case would be if the underlying OS were to accept anything you try to write into the socket..." Sent from my iPhone On Jan 8, 2013, at 9:21 AM, Emmanuel Lécharny <[email protected]> wrote: > One possible case would be if the underlying OS were to accept anything > you try to write into the socke
