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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=75526 --- shadow/75526 2005-07-31 17:55:53.000000000 -0400 +++ shadow/75526.tmp.2362 2005-08-29 05:06:58.000000000 -0400 @@ -81,6 +81,23 @@ Read 2 After the first read it gives up. If I changed my stream impl to block after the first read, the problem the reporter experienced would happen + +------- Additional Comments From [EMAIL PROTECTED] 2005-08-29 05:06 ------- +Ben, while this is indeed a different behaviour, I think it doesn't +matter that much (at least for this bug). The problem Alexander +described (and which I stumbled upon right now as well in v1.1.8.3) is +that StreamReader does not return at all if not all of the bytes are +available and the end of stream is not recognized(?) + +My problem: I have an XmlTextReader using a TextReader (StreamReader) +from a network connection. XmlTextReader eventually tries to read 1024 +bytes, but the whole request is only 112 bytes long. This causes +XmlTextReader.Read() to block until there is a timeout and the +connection is torn down. + +(you can test this with http://xmlrpccs.sourceforge.net/ when running +the SampleServer and SampleClient) + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
