28-07-2009, 09:23 PM
Hum, wait, sry. I mean... this limitation because of the FD_SETSIZE, but it's only when you are using C++ and working with pure winsocket. That happens because it uses the WaitForMultipleEvents function, and this function use the FD_SETSIZE as a limit of the array you pass in.
The .Net Framework abstracts that, so I'm pretty sure you can handle 65536 connections without no problem. Anyway, this is the handler thread. The execution should be handles by several threads, and then, there is no problem with one thread per packet handling, since the time you will spend to handle each one of this packets are quite small.
The .Net Framework abstracts that, so I'm pretty sure you can handle 65536 connections without no problem. Anyway, this is the handler thread. The execution should be handles by several threads, and then, there is no problem with one thread per packet handling, since the time you will spend to handle each one of this packets are quite small.