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

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

--- shadow/38136	Sat Feb 15 01:22:32 2003
+++ shadow/38136.tmp.10295	Sat Feb 15 05:36:54 2003
@@ -1,12 +1,12 @@
 Bug#: 38136
 Product: Mono/Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: NEEDINFO   
 Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: System
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: alp@atoker.com               
@@ -77,6 +77,41 @@
 JabberClient.Login (wild guess: crypto code fails?).
 
 ------- Additional Comments From gonzalo@ximian.com  2003-02-15 01:22 -------
 Created an attachment (id=3376)
 Proposed patch
 
+
+------- Additional Comments From dick@ximian.com  2003-02-15 05:36 -------
+Connect is _supposed_ to throw an "in progress" SocketException on non
+blocking sockets.  It happens on the ms runtime too:
+
+using System.Net;
+using System.Net.Sockets;
+using System;
+
+public class Test
+{
+        public static void Main()
+        {
+                Socket socket=new Socket(AddressFamily.InterNetwork,
+SocketType.Stream, ProtocolType.IP);
+                socket.Blocking=false;
+
+                socket.Connect(new
+IPEndPoint(IPAddress.Parse("192.168.59.200"), 1234));
+        }
+}
+
+$ ./sockblock.exe 
+
+Unhandled Exception: System.Net.Sockets.SocketException: A
+non-blocking socket operation could not be completed immediately
+   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
+   at Test.Main()
+(null)
+
+
+So unless the jabber client exhibits different behaviour on the ms
+runtime, this is not a bug.
+
+Marking as Needinfo.