C# TCP socket, asynchronous read and write at the “same” time (.NET CF), how?

Question

At the first look when using asynchronous methods on the socket level, there shouldn't be problems with sending and receiving data from the associated network stream, or 'directly' on the socket. But, you already probably know, there is.

The problem is particularly highlighted on the platform and the . 平台和上特别突出了该问题。

I use , BeginReceive and the callback function which performs ends a pending asynchronous read for the received data (EndReceive) from the async. ，BeginReceive和回调函数来结束从异步接收的数据（EndReceive）的挂起异步读取。 result.

As i need to constantly receive data from the socket, there is a loop which waits for the data. The problems begins when i want to send data. For that purposes before sending some data through the socket i'm "forcing" ends of asynchronous read with EndReceive. There is a great on that (sometimes you just can't wait for this ). （有时您不能等待此 ）。 Timeout is too long, and . 。 I don't want to close the socket and reconnect.

I use synchronous method Send for sending data (although the results are the same with async. methods BeginSend/EndSend). When sending is finished, i start to receive data again.

Resources that i know about:

• stackoverflow.com...properly-handling-network-timeouts-on-windows-ce - comment about timeouts,
• developerfusion.com...socket-programming-in-c-part-2/ - solution for simple client/server using asynchronous methods for receiving and synchronous method Send for sending data.

PS:I tried to send the data without ending asynchronous receive but then i got (ErrorCode: 10036). （错误代码：10036）。

Thanks in advance! I hope that i'm not alone in this 'one little problem'..

Answer 1

Have you considered to use Poll (or Select for multiple sockets) static method instead of BeginReceive to check if there are data for read? In my opinion this is causing you the trouble.