quote:Original post by Magmai Kai Holmlor
If your app is written correctly, it will only be placed in the scheduling queue when and if it has work to do (i.e. Event Driven, No Polling!).
This is true for a client side application with one or a few threads, but not for a server side application designed to server thousands of users per second.
If you write a server side application and create one thread per user you will be able to handle a significantly lower number of users compared to using async i/o. Async i/o and i/o completion ports is the way to go (refer to MSDN articles about server programming, or Jeffrey Richter''s books dealing with this.
