Asynchronous sockets and message queues
C#
1
Posts
1
Posters
0
Views
1
Watching
-
When using non-blocking I/O in C++ a simple send() call could fail with WSAEWOULDBLOCK and the data is put in a message queue. When a FD_WRITE is coming in you can try send it again. I wonder if this can happen with asynchronous sockets in .NET? Can a send fail with WSAEWOULDBLOCK so that I need to use a message queue or does the framework do the second send for me? Rickard Andersson Here is my card, contact me later! UIN: 50302279 Sonork: 37318