Google’s SPDY protocol would soon become non-existent in the Chrome browsers. The SPDY protocol supported features to hasten web browsing and downloads. Introduced in 2009, this was specifically to improve the speed of the web browser Chrome. Websites enabled with SPDY are more secure making developers use the protocol.
SPDY had replaced HTTP which was considered slow and insecure. However, a newer version of HTTP/2 is on its way, announced Google enabler Bence Bèky and Chris Bentzel. This new version will also replace some other existing support protocols like TLS (Transport Layer Security Extension) and NPN (Next Protocol Negotiation). NPN will be replaced by ALPN which stands for Application Layer Protocol Negotiation.
Also Read: Who Wins The Battle Between Google Plus And LinkedIn?
These new extensions will be rolled out in the newest version of Chrome i.e. Chrome 40.
SPDY was launched in 2009 as a research project by Googlers Roberto Peon and Mike Belshe. Their main target was to build a protocol that would let users browse through the web faster. The experiment was mainly to create a smoother channel between the server and web browser. SPDY was engineered in a way that pulled down latency. The multiplexed streaming feature and request prioritization enabled faster browsing experience for the users.
The SPDY protocol with negotiation and prioritization allowed multiple file streaming from the server. This resulted in quicker exchange of files between the server and client. Peter Bright of Ars Technica said, “SPDY’s major goals were to reduce latency and improve security.”
However, the features that SPDY supported have been engineered and incorporated in the latest version of HTTP/2. This protocol is favored over HTTP as it is supported by industry consensus. HTTP/2 uses the internet network much more efficiently than SPDY. The compression of header field and smooth multiple connectivity that allows multiple concurrent messages.
Other than this, HTTP/2 allows servers and clients to choose the protocol that they wish to use, which can be HTTP1.1 or HTTP 2.0 or any other protocol. The compatibility with HTTP 1 makes its all the more useful helping compress headers. With the option of multiplexing, web pages load much faster and more secure than SPDY. HTTP/2 has been engineered in such a way that it supports all devices from desktop to smartphones to tablets. It also supports various proxy servers, scales and delivery networks.
Google has announced that it will stop supporting SPDY protocol from the first quarter of 2016.It will also disable other supporting extensions along with SPDY protocol. This is mainly to redirect web users to shift to HTTP/2 which is flaunted as a more secure and faster version of HTTP that would enable quicker web bro