-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 11/6/2009 3:02 AM, André Warnier wrote: > But, during a keepalive connection, usually the server needs to dedicate > one process, or child or thread, to this connection. So this > child/thread is blocked, and cannot server requests from other browsers. > > If the KeepAlive timeout is very long, it means that when the browser > has finished requesting all the objects from the page, the connection > still stays alive for a while, because the server waits to see if there > are no more requests coming on the connection. Or, the client can close the connection which is a pretty good way to decide that there are no more requests to be made on that connection. Note that Tomcat's NIO connector puts worker threads back into the thread pool between keepalive requests on a single connection, and you can get better thread usage in that way. > I would think that nowadays, a setting of 3 sec. is largely sufficient > in most cases. +1 If the client can't make another request in a keepalive connection fast enough, it can always open up a new connection and make a new request. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkr5xYQACgkQ9CaO5/Lv0PA4iACfXjrmHkgcEAd47RTcMgmyPChF /mgAnRHLk2CSnliOOe+ROD4EUFxm8CBU =GP7F -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
