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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79878 --- shadow/79878 2007-01-17 06:19:34.000000000 -0500 +++ shadow/79878.tmp.2749 2007-01-17 12:19:59.000000000 -0500 @@ -1,13 +1,13 @@ Bug#: 79878 Product: Mono: Class Libraries Version: 1.1 OS: unknown OS Details: -Status: RESOLVED -Resolution: FIXED +Status: REOPENED +Resolution: Severity: Unknown Priority: Major Component: System AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] @@ -106,6 +106,14 @@ it's still available to the user code though. Perhaps you can use one of the techniques described here http://cr.yp.to/docs/connect.html to figure out the connection status? In any case, perhaps you should consider calling GetSocketOption in the Select/Poll implementation only if the Connected flag is false (instead of calling it all the time if the socket is writable). + +------- Additional Comments From [EMAIL PROTECTED] 2007-01-17 12:19 ------- +Could you point me directly to the Ice tests? (The directory in the +source tar is fine.) + +I looked at the DJB page, but I don't think any of the techniques he +listed is suitable for mono. I'll have a look at only checking the +SO_ERROR state if connected == false though. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
