It sounds like you already know everything there is. How great it must be to have enlightenment such as your own.
This was a very well structured and thought out article. It is actually identical to an article I have been wanting to write for a while. Few things I might have added as an addition, being that while the spec notes 2 open connections per host, most browser these days allow considerably more.
> Chrome allows 6 connections per hostname
> FF allows 6 connections per hostname
Even the iPhone allows 4 connections per hostname.
Good job on the article. Exactly as you say, even if one person doesn't find it useful, doesn't mean other people share the same sentiments!
I'm not sure if you are being sarcastic, or serious, but it's pretty common practice to "hack" around particular provisions noted in lots of different specs in order to provide a faster browsing speed (perceived or actual for the user).
Just a few lines later the spec specifically says that:
> "This change applies to the initial window of the connection in the
> first round trip time (RTT) of data transmission following the TCP three-way handshake."
Well, guess what, lots of large companies ignore this, and they start with a much larger initial window. They do this in order to shave off as many round trips as possible, to reduce your load time. (Google AMZ Apple etc)
This was a very well structured and thought out article. It is actually identical to an article I have been wanting to write for a while. Few things I might have added as an addition, being that while the spec notes 2 open connections per host, most browser these days allow considerably more.
> Chrome allows 6 connections per hostname > FF allows 6 connections per hostname Even the iPhone allows 4 connections per hostname.
Good job on the article. Exactly as you say, even if one person doesn't find it useful, doesn't mean other people share the same sentiments!