On Sep 29, 2006, at 8:39 AM, Filip Hanik - Dev Lists wrote:
Remy Maucherat wrote:
[EMAIL PROTECTED] wrote:
Author: mturk
Date: Fri Sep 29 01:23:37 2006
New Revision: 451157
URL: http://svn.apache.org/viewvc?view=rev&rev=451157
Log:
Introduce keepAliveTimeout to be able to separate
the Keep-Alive and Socket timeout.
The patch enables to have infinite socket timeouts
while still having correct keep alive.
As I said before, I see no point in that.
maybe I'm being dumb here, so please enlighten me, but how are they
(keepalivetimeout vs connection timeout) different on a HTTP
connection?
wouldn't the smallest of these two values always close the connection?
connection timeout on HTTP is after all only measured when the
worker thread is not using the connection. on java.io, it would be
on a read() from the input stream, and on APR and NIO it would be
time spent in the poller or a read()
Usually the keepalive is < the normal timout. Keepalive
timeouts only apply on those connections in that mode.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
