Chava Leviatan wrote: > Are there any "rules" for setting how many connections will be handled > by one thread when > using the pool thread method ? It greatly depends on the amount of offline processing that needs to be done.
If, like netchat, it is mostly a case of "receive, compare, send", then a single thread can handle everything. If it's a case of "receive, compute mandelbrot encrypted with an AES key you need to brute force", if you don't assign one thread per socket you will end up with an application that receives X connections (where X is the number of threads you have), and then stops responding. Middle ground cases will fit, well, the middle ground. > Chava Shachar ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]