> Do you really think that a single task can handle 100 sockets open to
> 100 clients in an efficient manner?
>
> Now, I don't KNOW what the number is. But I do KNOW that the number is
> not "N"! Having some kind of enforced limit causes one to design code
> rather than just winging it.
Some servers, like muds and SQL servers, have no options but to handle all
the clients from one process. These servers could benifit from threads,
but they can't spawn of childs becouse of the communication between the
processes would be far to complicated and massive.
All the big muds I know handles several hundreds of clients from one task,
so the answer to your question is yes.
Baldur