[Mono-bugs] [Bug 74724][Nor] New - System.Net.Sockets.NetworkStream.CanRead behaviour incorrect

[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 mhinks@gmail.com.

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

--- shadow/74724	2005-04-25 11:32:12.000000000 -0400
+++ shadow/74724.tmp.1046	2005-04-25 11:32:12.000000000 -0400
@@ -0,0 +1,47 @@
+Bug#: 74724
+Product: Mono: Class Libraries
+Version: 1.1
+OS: Debian Woody
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: mhinks@gmail.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: System.Net.Sockets.NetworkStream.CanRead behaviour incorrect
+
+Description of Problem:
+
+Difference between behaviour of .NET Framework 1.1 and Mono Class Library 
+when using System.Net.Sockets.NetworkStream.CanRead. 
+
+Throws "EndRead failure" when no data is available.
+
+
+Steps to reproduce the problem:
+1. Instanciate an asynchronous socket and connect it to an endpoint.
+2. Use a System.Net.Sockets.NetworkStream as your means of 
+reading/writing data.
+3. [NetworkStream].BeginRead(x, x, x, Read_Method, null);
+4. Use "if ([NetworkStream].CanRead)" to test whether the stream is 
+readable inside your Read_Method async_callback
+
+Actual Results:
+
+Exception: "EndRead Failure"
+
+Expected Results:
+
+Boolean return value.
+
+How often does this happen? 
+
+Every time.
+
+Additional Information: