RE: Of HTTP/1.1 persistent connections and TCP Keepalive timers

What experimentation, if any, has been done with adaptive server timeouts? A
project I'm working on reduces timeouts based on current load. When a
certain point is reached connections are closed immediately until the load
drops down.

I haven't got as far as testing this on a live site so I'm curious whether
anyone has any real world experience.

> -----Original Message-----
> From: Fielding, Roy [mailto:fielding@eBuilt.com]
> Sent: Thursday, November 02, 2000 1:08 PM
> To: 'Jeff.Hodges@kingsmountain.com'; http-wg@hplb.hpl.hp.com
> Subject: RE: Of HTTP/1.1 persistent connections and TCP 
> Keepalive timers
> 
> 
> The decision on when to close is left to either side.  A server will
> close the connection based on its resource-consumption requirements
> which may vary substantially based on the type of server and the
> number of clients it is intended to serve.  A client will close the
> connection if it is connection-limited and needs to open many other
> connections, or if it just believes in being network friendly.
> 
> Unfortunately, none of the major browsers are network friendly,
> so they typically ignore the connection (not even recognizing FIN
> as an event) until they later attempt to use it again.  Most
> general-purpose servers have a short activity time-out on
> connections and will close the connection after that time-out
> (typically under 10 seconds, though a high-activity server will
> set this to one second or turn off persistent connections altogether).
> 
> Cheers,
> 
> Roy T. Fielding, Chief Scientist, eBuilt, Inc.            
> (www.ebuilt.com)
>                  Chairman, The Apache Software Foundation 
(www.apache.org)

Received on Thursday, 2 November 2000 10:23:02 UTC