Speeding up the web is on Microsoft’s agenda as they plan on submitting a proposal for a quicker Internet protocol to the standards body responsible for the development of HTTP 2.0. The standards body would have to be the IETF – Internet Engineering Task Force which will be having a meeting this week for discussing the future of the HTTP (hyper text transfer protocol). One of the topics is developing HTTP 2.0, which promises to be a modern and faster approach to Internet communication.
One of the strong candidates for this new HTTP 2.0 is the SPDY protocol created by web giant Google. The “speedy” protocol as it is pronounced is the proposal coming from Google to replace the aging HTTP protocol which you probably know is the language that is being used now when the web browser “talks” to a web server. When you are requesting for a webpage from a server, most likely the browser sends this request via HTTP. The server will give the answer using HTTP as well, this being the reason why at the start of many websites you notice “http”.
Clik here to view.
SPDY Protocol
The aforementioned SPDY protocol created by Google is capable of handling all of the tasks that HTTP is taking care of, but it can do these 50% quicker. Firefox and Chrome already offer support for SPDY and there are some big websites such as Twitter and Google that are offering web pages over SPDY.
The agenda of IETF’s meeting for this week is to discuss the proposal of implementing the SPDY protocol and what it will take to turn it into a standard. The thing is that Microsoft wants to submit a different protocol in the form of the HTTP Speed+Mobility. Even though its name is not as cool as SPDY, it seems to cover just about all of the territory of Google’s protocol. Details regarding this new protocol are rather scarce at the moment but it seems that it also comes with several improvements drawn from the development of the HTML5 WebSockets API.
It will be quite a difficult process to implement a new replacement for the HTTP which will be faster since it’s harder than just selecting one and then standardizing it. Most likely, the IETF is going to gather all the great ideas from both sides and merge them into a new protocol which will be capable of speeding our beloved WWW.
11
