W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 2000

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

From: Fielding, Roy <fielding@eBuilt.com>
Date: Thu, 2 Nov 2000 10:08:27 -0800
Message-ID: <AA1E32BC8A58D411A2CB0050DACEDA4366074C@raptor>
To: "'Jeff.Hodges@kingsmountain.com'" <Jeff.Hodges@kingsmountain.com>, http-wg@hplb.hpl.hp.com
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 18:10:24 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:40 EDT