Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Before you decide that you need 'alternatives to winsock2" please read this: <a href="http://rads.stackoverflow.com/amzn/click/0735615799" rel="nofollow noreferrer">Network Programming for Microsoft Windows</a>.</p> <p>In summary, you DON'T need an 'alternative to Winsock2' you need to understand how to use the programming models supplied to full effect on the platform that you're targeting. Then, if you really <strong><em>need</em></strong> cross platform sockets code that uses async I/O then look at ASIO, but, if you don't <em>really need</em> cross platform code then consider something that actually focuses on the problems that you might have on the platform that you do need to focus on - i.e. something windows specific. Go back to the book mentioned above and take a look at the various options you have. </p> <p>The most performant and scalable option is to use IO Completion Ports. I have some free code available from <a href="http://www.serverframework.com/products---the-free-framework.html" rel="nofollow noreferrer">here</a> that makes it pretty easy to write a server that scales and performs well on a windows (NT) based platform; the linked page also links to some articles that I've written about this. A comparison of my framework to ASIO can be found here: <a href="http://www.lenholgate.com/blog/2008/09/how-does-the-socket-server-framework-compare-to-boostasio.html" rel="nofollow noreferrer">http://www.lenholgate.com/blog/2008/09/how-does-the-socket-server-framework-compare-to-boostasio.html</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload