[Mono-bugs] [Bug 71588][Wis] New - Async Socket BeginRead not functioning properly

[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 grompf@sublimeintervention.com.

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

--- shadow/71588	2005-01-21 15:56:01.000000000 -0500
+++ shadow/71588.tmp.626	2005-01-21 15:56:01.000000000 -0500
@@ -0,0 +1,52 @@
+Bug#: 71588
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: OSX 10.3.7
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: CORLIB
+AssignedTo: gonzalo@ximian.com                            
+ReportedBy: grompf@sublimeintervention.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Async Socket BeginRead not functioning properly
+
+The attached code below does not work as expected on Mono SVN HEAD.
+
+The behaviour on MS.NET is:
+
+C:\>monod-server.exe
+Begin receive on: 444 (SERVER: 520)
+RECEIVED COMMAND (7): INSTALL
+
+C:\>monod-client.exe
+WROTE!
+
+On Mono:
+
+plasma@dionysus ~$ mono monod-client.exe
+WROTE!
+
+plasma@dionysus ~$ mono monod-server.exe
+Begin receive on: 9 (SERVER: 8)
+
+Mixing and matching the client and server between the runtimes gives:
+
+MONO client + MONO server: Failure
+MONO client + MS server: Success
+MS client + MONO server: Failure
+MS client + MS server: Success
+
+Additionally its worth noting that the Server.cs starts 52 threads when it starts up.  For a .Listen 
+(5) this seems incredibly excessive.
+
+Also; this code was tested with IPEndPoints, and UnixEndPoints (mono only).
+
+-kangaroo
+
+PS> Assigning to gonzalo as per his request.