Google SPDY: life after HTTP 1.1
Since January 19, 2011 support for the SPDY (SPeeDY) protocol has appeared in the Chrome browser, it is also enabled for SSL traffic on Google servers. Thus, all sites owned by Google are loaded much faster in Chrome than in any other browser. For four months, Chrome users receive many pages from Google sites not using HTTP at all.
This may remind someone the situation with Microsoft, which “improved” standards in IE browser so that IIS servers respond faster than Apache. But here the situation is radically different. This is not about getting some kind of monopoly, but about providing fast Internet for everyone , which is beneficial for Google a priori.
The SPDY protocol is completely open . Owners of any server (for example, here’s a module for Apache ) can raise the corresponding proxy, and developers of any browser can implement customer support.
Instead of replacing the standard, an experimental and open extension is proposed here. This is the best approach to improve common standards that cannot be replaced in one fell swoop. Even Microsoft proved the effectiveness of this approach when releasing such extensions of standards (for example, the concept of XMLHTTPRequest was proposed by the developers of Outlook Web Access for Microsoft Exchange Server 2000).
')
The current version of HTTP 1.1 was developed in 1996, when the web was much simpler, so now HTTP has become a bottleneck that can be expanded withHTTP 1.2 SPDY. The improved version of HTTP speeds up web pages loading by 44–64% due to various tricks : multiplexing requests, setting priorities for requests, compressing HTTP headers.
Previously, SPDY was implemented only in a separate experimental build of Chrome , but now the protocol has finally been brought to readiness and it seems that global changes in the draft standard are not expected. SPDY is based on TCP and Google confidently states that it will not harm the integrity of the Network.
SPDY connections in the Chrome browser can be viewed in real time by typing chrome: // net-internals in the address bar, go to the SPDY tab and click View live SPDY sessions ( screenshot ).
This may remind someone the situation with Microsoft, which “improved” standards in IE browser so that IIS servers respond faster than Apache. But here the situation is radically different. This is not about getting some kind of monopoly, but about providing fast Internet for everyone , which is beneficial for Google a priori.
The SPDY protocol is completely open . Owners of any server (for example, here’s a module for Apache ) can raise the corresponding proxy, and developers of any browser can implement customer support.
Instead of replacing the standard, an experimental and open extension is proposed here. This is the best approach to improve common standards that cannot be replaced in one fell swoop. Even Microsoft proved the effectiveness of this approach when releasing such extensions of standards (for example, the concept of XMLHTTPRequest was proposed by the developers of Outlook Web Access for Microsoft Exchange Server 2000).
')
The current version of HTTP 1.1 was developed in 1996, when the web was much simpler, so now HTTP has become a bottleneck that can be expanded with
Previously, SPDY was implemented only in a separate experimental build of Chrome , but now the protocol has finally been brought to readiness and it seems that global changes in the draft standard are not expected. SPDY is based on TCP and Google confidently states that it will not harm the integrity of the Network.
SPDY connections in the Chrome browser can be viewed in real time by typing chrome: // net-internals in the address bar, go to the SPDY tab and click View live SPDY sessions ( screenshot ).
Source: https://habr.com/ru/post/117230/
All Articles