[Mono-bugs] [Bug 74840][Maj] Changed - Blocking Read() does not return if NetworkStream is closed underneath it

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by joeshaw@novell.com.

http://bugzilla.ximian.com/show_bug.cgi?id=74840

--- shadow/74840	2005-05-05 21:29:33.000000000 -0400
+++ shadow/74840.tmp.7191	2005-05-09 14:11:47.000000000 -0400
@@ -82,6 +82,15 @@
 <gonzalo> All clients closed
 <gonzalo> Read 2
 <gonzalo> Read 2 bytes
 <gonzalo> Reading data
 <gonzalo> and then a nullref + objectdisposed
 <gonzalo> so our behavior matches MS except for that extra nullref
+
+------- Additional Comments From joeshaw@novell.com  2005-05-09 14:11 -------
+Sigh.  That behavior is so broken.
+
+What are my alternatives here?  I'd rather not do async IO, since each
+connection is being handled by its own thread and I don't need the
+added complexity.  Can I do a Thread.Abort() on that thread after
+closing the socket?  Will that cause the Read() to end?  What would
+you recommend?