Costin Manolache wrote:
Yes, 100 concurent requests is a sign you need lb - serving 1000 on
Sometimes it is desired to have the capability of serving 1000 concurrent connections (not requests). The typical situation is when the frontend server is used for delivering a static content with higher concurrency then backend application server. The thread per request model like implemented with APR connector solves this problem. NIO would need AJP protocol implementation to be able to do that as well.
one server is a false problem in most cases. I would rather have a server smartly reject requests and notify a lb rather then degrading all requests by accepting more than it can handle properly.
Agreed, but without some sort of IPC it's impossible. Regards, Mladen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
