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

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). ie, RFC 3390 ( http://www.rfc-editor.org/rfc/rfc3390.txt http://www.rfc-editor.org/rfc/rfc3390.txt ), provides algorithms for determining/detecting the maximum initial window for TCP traffic. min (4MSS, max (2MSS, 4380 bytes)) 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 spec was written 10 years ago! (Read here for more information http://blog.benstrong.com/2010/11/google-and-microsoft-cheat-on-slow.html http://blog.benstrong.com/2010/11/google-and-microsoft-cheat... )