Archived

This topic is now archived and is closed to further replies.

Async sockets in .NET

This topic is 5125 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Well, these are definitely unique. I have a few questions, I am used to Unix-style select() and WSAAsyncSelect methods of socket I/O. 1. I don''t understand the significance of the state object. Is this so you can differentiate between multiple items in the callbacks? 2. It seems like its overlapped I/O more than anything else. If I''m used to simply waiting for a FD_READ message and acting on it, do I have to call Socket.BeginReceive at the end of my Receive callback to get the same effect? 3. What socket model does the framework use on Win98 if 98 doesn''t support I/O completion ports? 4. Aren''t I/O completion ports a bit heavyweight for some applications? Thanks.

Share this post


Link to post
Share on other sites