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

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Sat, 15 Feb 2003 17:12:38 -0500 (EST)


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 16:12:32 2003
+++ shadow/38136.tmp.7044	Sat Feb 15 17:12:38 2003
@@ -1,17 +1,17 @@
 Bug#: 38136
 Product: Mono/Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: REOPENED   
+Status: NEW   
 Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: System
-AssignedTo: mono-bugs@ximian.com                            
+AssignedTo: gonzalo@ximian.com                            
 ReportedBy: alp@atoker.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Summary: System.Net.Sockets.Socket exception when connecting
 
@@ -128,6 +128,9 @@
 BeginConnect works fine with the MS runtime and a non-blocking socket
 and mono does not.
 
 ------- Additional Comments From dick@ximian.com  2003-02-15 16:12 -------
 In that case the async Connect method in Socket.cs should be catching
 the exception and Poll()ing for completion, not the runtime code.
+
+------- Additional Comments From gonzalo@ximian.com  2003-02-15 17:12 -------
+Ok. I'll do it.