[Mono-bugs] [Bug 71933][Min] New - ReceiveTimeout and SendTimeout on asynchronous sockets

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 28 Jan 2005 17:16:03 -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 aksdb@gmx.de.


--- shadow/71933	2005-01-28 17:16:03.000000000 -0500
+++ shadow/71933.tmp.21458	2005-01-28 17:16:03.000000000 -0500
@@ -0,0 +1,51 @@
+Bug#: 71933
+Product: Mono: Class Libraries
+Version: 1.1
+OS: Debian Woody
+OS Details: 
+Status: NEW   
+Priority: Minor
+Component: System
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: aksdb@gmx.de               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: ReceiveTimeout and SendTimeout on asynchronous sockets
+Description of Problem:
+If I set a ReceiveTimeout or SendTimeout on a socket, they are used even
+when I use the socket asynchronous (BeginReceive/BeginSend).
+This should not be the case according to MSDN.
+Supported by the .NET Compact Framework.
+Receive time out. This option applies only to synchronous methods; it has
+no effect on asynchronous methods such as BeginSend."
+Steps to reproduce the problem:
+(the following is no real code excerpt, it is just meant to demonstrate
+what I mean)
+Socket s = new Socket(...);
+s.SetSocketOption( SocketOptionLevel.Socket,
+SocketOptionName.ReceiveTimeout, 15000 );
+s.SetSocketOption( SocketOptionLevel.Socket, SocketOptionName.SendTimeout,
+15000 );
+Actual Results:
+The connection times out after the given 15 seconds.
+Expected Results:
+The connection should not time out as I started an asynchronous call.
+How often does this happen? 
+Additional Information: