h visli wrote: > I have more than 3000 clients. I do not hope that each client to bound a > thread.
And why is that? FUD? (Fear, Uncertainty, Doubt?) Doing "a client per thread" is a normal way of handling things in Windows. Ok, you have a tiny overhead from the context switch between different threads, but that is way lower than using a single thread to handle multiple connections and for each read-write cycles attempting to determine by your own code the answer to such questions as "who is talking to me" and "to whom should i be responding". For the record, I've had a server written in Synapse that had little over 14000 users connected at peak, and normally have around 8000-9000 connections all the time - all of them "talking" and "listening" more or less constantly. Each of those connections was implemented using it's own thread... and it ran indeed rather smoothly, so your 3000+ concurrent users isn't actually very much :) -- Markku Uttula ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
