[Mono-bugs] [Bug 75526][Nor] Changed - StreamReader blocks on reading too much

[bugzilla-daemon at 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 dseifert at gmx.de.

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

--- shadow/75526	2005-08-29 15:30:14.000000000 -0400
+++ shadow/75526.tmp.22602	2005-08-30 04:19:49.000000000 -0400
@@ -107,6 +107,27 @@
 
 i think your problem is caused by the XmlTextReader behaviour. Or it
 is at least under MS .NET. Look at this Thread:
 http://mail.jabber.org/pipermail/jabber-net/2004-September/thread.html#353
 
 Alex
+
+------- Additional Comments From dseifert at gmx.de  2005-08-30 04:19 -------
+Yes,
+http://mail.jabber.org/pipermail/jabber-net/2004-September/000360.html
+describes it well (though in my case it wasn't 4k but only 1k with
+Mono), but I am not sure it is the same problem as this one.
+
+I think because XmlTextReader only calls the underlying stream's Read
+function, my problem comes back right away to your StreamReader bug
+report. If StreamReader (based on a NetworkStream) would return
+immediately like MS .NET if no more data is available (which in case
+of a network stream may well be before all data is received and I
+think this is where the actual problem has risen from conceptionally),
+this would not be an issue. 
+
+In the case of http://xmlrpccs.sourceforge.net I now fixed the problem
+by copying the contents of the network stream (lenght is known because
+of the Content-Length field of the POST request) into a string and
+using this as the buffer to read from (in which case the end of stream
+is recognizable).
+