WvSockStream: write() should catch exceptions like read() does.
commit6940d6c230d6872c638322b5bcbf2d6b1b409fb9
authorAvery Pennarun <apenwarr@gmail.com>
Thu, 2 Oct 2008 19:48:25 +0000 (2 15:48 -0400)
committerAvery Pennarun <apenwarr@gmail.com>
Thu, 2 Oct 2008 19:48:25 +0000 (2 15:48 -0400)
tree4ad86ff3b3dfd38e8738ea4d06dc68f796d8af1e
parent86debbe4b373a0b4615b5868b1fd3b23569b326a
WvSockStream: write() should catch exceptions like read() does.

This didn't happen for me, but pmccurdy saw some EWOULDBLOCK errors; it
might be mono version dependent.  In any case, EWOULDBLOCK isn't an error in
the case of a non-blocking socket, it's just an advisory, so we do what's
appropriate.
wvdotnet/wvsockstream.cs