tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject RE: [VOTE] Split soTimeout to soTimeout and keepAliveTimeout
Date Mon, 02 Oct 2006 17:36:43 GMT

> -----Original Message-----
> From: Mladen Turk [] 
> Sent: Monday, October 02, 2006 4:25 AM
> To: tomcat Developers List
> Subject: [VOTE] Split soTimeout to soTimeout and keepAliveTimeout
> Hi all,
> I would like to propose a simple vote on the thing I consider
> as very important. It's probably the first vote ever done for
> the commited code, but the reasons are known for the folks reading
> tomcat dev list.
> The things we have right now for dealing with Keep-Alive is
> dependent only on the soTimeout.
> I propose that we split that to the real soTimeout which is the
> timeout between two consecutive read() on http request and the
> additional keepAliveTimeout that will be used for determining the
> timeout between two requests.
> Few reason why we should need those timeouts separately
> configured is:
> 1. Why not, if its possible without breaking current config ?
> 2. If the timeout between two request is lower then soTimeout it
>     will allow to have much higher number of slow clients
> 3. If the timeout between two requests is higher then soTimeout
>     it will allow to deal with slow clients sending one byte at the
>     the time with the unacceptable rate.

I pretty much agree with Remy:  Anything useful this would do has been in
place since the early days of Coyote.  Also, anybody that actually would
care about this option almost certainly wouldn't be using the JIO Connector

> So, I'll just throw a vote here:
> [ ] I'm for that proposal
> [ ] I'm against that proposal
> [X] I don't care
> Of course, there is always an option to have an veto.
> As many of you already know, the code itself was already
> in the SVN, but it was reverted.
> Regards,
> Mladen.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message