[Mono-bugs] [Bug 528344] New: Socket ConnectAsync, ReceiveAsync, SendAsync methods and non-blocking sockets.

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=528344


           Summary: Socket ConnectAsync, ReceiveAsync, SendAsync methods
                    and non-blocking sockets.
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: benoit at zeroc.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Created an attachment (id=310655)
 --> (http://bugzilla.novell.com/attachment.cgi?id=310655)
testcase

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_7; en-us)
AppleWebKit/530.19.2 (KHTML, like Gecko) Version/4.0.2 Safari/530.19

The implementation of the new socket async API doesn't seem to work very well
with non-blocking sockets.

ReadAsync fails with a WouldBlock error, ConnectAsync reports success even
though the connection is refused (on Linux at least, on OS X, it hangs
indefinitely). I didn't check SendAsync but I suspect it would also report
WouldBlock if the send can't complete immediately.

Here's a test case for ConnectAsync, let me know if you need a test case for
ReceiveAsync/SendAsync too.





Reproducible: Always

Steps to Reproduce:
1. compile test.cs
2. run test.exe
3.
Actual Results:  
On OS X, it hangs.
On Linux, it reports "connect succeeded"

Expected Results:  
It should report "ConnectionRefused" (which it does with a blocking socket).

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.