[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wget
Subject:    Multiple connections to single host
From:       Micah Cowan <micah () cowan ! name>
Date:       2008-01-21 22:08:03
Message-ID: 479517C3.2030407 () cowan ! name
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So, RFC 2616 strongly suggests (but does not require) that only at most
two persistent HTTP connections to a given host be maintained.

However, note that this
  1. Does not apply to non-HTTP connections (such as FTP)
  2. Does not apply to non-persisting (HTTP/1.0 or "Connection: close")
connections.

This means that the relevant text doesn't say anything about how many
connections could be used to fetch a given resource (a lá "download
accelerators"), provided none of the connections are persistent (they'll
 all be closed afterwards).

It also means that, while one might interpret it to limit the number of
HTTP connections to a given host, it doesn't say anything about opening
an additional couple (or several) connections over some other Layer 7
protocol(s) to the same host.

What do you think? My inclination is still to use a hard limit for _all_
types of connections, HTTP or otherwise. A case might be made that users
should be allowed to open more than 2, by request, but I wouldn't want
to go much beyond that (and in fact, am disinclined to go beyond it at all).

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHlRfD7M8hyUobTrERAiejAJ9l8RHHP0iwK+KbtzsdiTojoVBRcwCfa1rz
h3Yx+tb3zRxuI0X9FJESoos=
=woWo
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]