[Mono-bugs] [Bug 74661][Nor] Changed - Asynchronous I/O not working with windows

[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 gonzalo@ximian.com.

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

--- shadow/74661	2005-04-19 14:18:25.000000000 -0400
+++ shadow/74661.tmp.32379	2005-04-19 17:55:13.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 74661
 Product: Mono: Class Libraries
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: XP
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: NOTABUG
+Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: dominic_ullmann@hispeed.ch               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -71,6 +71,26 @@
 therefore I'm not sure about this).
 
 ------- Additional Comments From dominic_ullmann@hispeed.ch  2005-04-19 14:18 -------
 Created an attachment (id=14976)
 test showing the problem
 
+
+------- Additional Comments From gonzalo@ximian.com  2005-04-19 17:55 -------
+The problem is in the test. No one is calling CloseConnection to close
+the socket or waiting for the write to finish on the client side.
+
+See TestClient.cs. When you call Send() this, in turn, calls
+task.StartNextPart(), which starts writing and finishes immediately,
+without waiting for the asyncrhonous task to finish.
+
+I changed StartSendNextPart to return the IAsyncResult from BeginWrite
+and then, in Test.Send:
+---
+IAsyncResult res = task.StartSendNextPart ();
+res.AsyncWaitHandle.WaitOne ();
+---
+
+and everything worked fine. On MS the client prints the 'write
+completed' message sometimes, but not always.
+
+