I'll share this with my brother he is sick with that of HTML. Like i see in that graph thats pretty nice enhancements from spyd over the http
You have some information that's not quite right.
HTTP/1.0 opens a connection for every request. HTTP/1.1 (which was ratified in 1999 and pretty much what any contemporary browser uses) does not open a connection for each web request.
Any contemporary browser maintains open connections to a contemporary web server via the HTTP/1.1 specification.
Furthermore, older browsers will be conservative in the number of connections they'll open against a web server. Contemporary web browsers will generally open six TCP connections so it's not quite as bad as you think.
Finally there's something few (technical) people know about, the HTTP/1.1 spec includes something called "HTTP pipelining" which allows an HTTP client, e.g., a browser, to request multiple elements at once.
To enable HTTP Pipelining in Firefox simply go to the URL edit box and type "about:config" then in the filter enter "pipe". In the results you'll see "network.http.pipelining", change that to "true" (by double clicking on the "false" value). While you're at it crank up maxrequests to 7 instead of 4. That's the number of elements to fetch at once.
Yes, SPDY would be faster if all web servers spoke it... but they don't. Only Google's web servers have any notable presence on the web as far as talking the SPDY protocol.
Lastly HTTP Pipelining makes an even *BIGGER* difference if you're on a higher latency connection, e.g., you're using tethering against your phone or perhaps you're using some 3G Aircard. That's because you're not waiting for round trip times on each and every distinct web resource mentioned on an HTML page you just hit. Firefox will just say, give me M elements, give me another M elements, etc., etc. (maxrequests) vs. asking for things one at a time.
See Chrome fanboys, it's not as über as you thought...
It was a great post until this:
>See Chrome fanboys, it's not as über as you thought...
Maybe is not as shitty as you want it to be.
Why use the TCP protocol? I suggest using the SCTP protocol instead. I mean one could tweak some things in the TCP protocol, but when looking at the future, SCTP might be a better solution. SCTP supports multiple steams over one connection and much more advantages over TCP connections.
It's about time... Firefox has had HTTP Pipelining since 2004... and truth be told, I do use Chrome, just nowhere as much as I do Firefox.
Because SCTP would require rewriting all web browsers and web servers and the only company that cared about SCTP was Sun and you know where they're at nowadays (R.I.P.) In other words none of the major client platforms come with SCTP.
SPDY just builds upon what's already there, i.e. TCP, the right decision.
the main advantage of speedy is that no modification of the current network infra is required.
facebook,wordpress,twitter already started to use and implement it.
NEWS TIPS |
This site is intended for informational and entertainment purposes only. The contents are the views and opinion of the author and/or hisassociates. All products and trademarks are the property of their respective owners. All content and graphical elements areCopyright © 1999 - 2013 David Altavilla and HotHardware.com, LLC. All rights reserved. Privacy and Terms