On Mon, 2 Aug 1999, Josh Cohen (Exchange) wrote:
> As it stands today, IE4 and IE5 will do HTTP/1.1 and persistent
> connections by default. Based on this, I would say there are
> a fair amount of persistent connections in use today.
But it is difficult to configure the clients to take benefit of HTTP/1.1
It would be nice to add TE: trailers,deflate for example.
> On a related note, I think one of the major issues, which hasn't
> been mentioned here yet, is the server utilization. From the
> web site's perspective, which handles hundreds of requests
> per second, holding a persistent connection open for even a mere
> second is very expensive. This is especially painful for servers
And establishing a connection for every request is quite expensive on the
network.
> that maintain a more or less fixed set of processes or maximum
> concurrent connections such as Apache.
That's an old design issue, when you design a HTTP/1.1 server you have to
take into account the fact that connections are persistent. A forking
server may not be the best answer there.
> I think that often, because of this, server admins choose to
> prioritize their own server resources over the health of the net.
Talking about cache and replication, it would be nice also to have more
and more server admins doing "the right thing" about Cache-Control
headers, it would avoid dirty hacks to see if a resource can be cached or
not...
/\ - Yves Lafon - World Wide Web Consortium -
/\ / \ Architecture Domain - Jigsaw Activity Leader
/ \ \/\
/ \ / \ http://www.w3.org/People/Lafon - ylafon@w3.org
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST