[Mono-bugs] [Bug 38136][Nor] Changed - System.Net.Sockets.Socket exception when connecting

[bugzilla-daemon@rocky.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=38136

--- shadow/38136	Sat Feb 15 05:36:54 2003
+++ shadow/38136.tmp.21626	Sat Feb 15 12:16:20 2003
@@ -1,12 +1,12 @@
 Bug#: 38136
 Product: Mono/Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEEDINFO   
+Status: REOPENED   
 Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: System
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: alp@atoker.com               
@@ -112,6 +112,18 @@
 
 
 So unless the jabber client exhibits different behaviour on the ms
 runtime, this is not a bug.
 
 Marking as Needinfo.
+
+------- Additional Comments From gonzalo@ximian.com  2003-02-15 12:16 -------
+Aha! Dick, your test works as expected (ie, throw the exception),
+however, the jabber client does something like this:
+
+socket.BeginConnect (new IPEndPoint (IPAddress.Parse("127.0.0.1"),
+1433), new AsyncCallback (Callback), socket);
+
+instead of just socket.Connect ().
+
+BeginConnect works fine with the MS runtime and a non-blocking socket
+and mono does not.