Microsoft explained the HTTP/2 protocol of IE and its significance to the Internet.

Microsoft explained the HTTP/2 protocol of IE and its significance to the Internet.

Microsoft is working to deploy HTTP/2 in its own IE browser, and this work started as early as it added the SPDY 8.1 protocol to Windows and Windows Phone 3.0. Of course, if you have used the Windows 10 technology preview version, you can now experience the latest standards. The company also wrote a special article to describe why this update is so important.
 

First, HTTP/2 is so important because HTTP/1 has limited functionality. When loading a webpage, the browser submits many different query requests to the server. Each query must wait for the server to respond before continuing the next query.

One solution to this restriction is to enable multiple connections, but it is difficult to strike a balance between the number of projects that can be simultaneously requested and server optimization.

HTTP/2 adopts long-lived connections and integrates multiple request technologies in single-or multi-channel connections, in order to improve efficiency (web page loading will also be faster ).

But how obvious is the improvement in efficiency? After research, Microsoft's Bing Department found that for every 10 ms of page loading time, the website needs to pay as much as $0.25 million in annual spending.

If the latency increases by 100 ms, online retailers may lose 1 percentage point in sales, because consumers do not want to waste time searching.

Therefore, for service providers, if you want to provide users with a seamless experience, it is very important to improve every millisecond!

In addition, mobile networks also benefit from HTTP/2. Because fewer connections are required but are more persistent, HTTP/2 puts less pressure on the network.

Imagine that billions of smartphone users around the world are connected at the same time, and the network is under great pressure.

· Finally, HTTP/2 will be fully backward compatible with HTTP/1.1. In this way, developers do not need to change various lib or application interfaces (APIS ).
 

Obviously, to make it a new industry standard, a smooth technological transition is crucial!
 

[Compiled from: Winbeta/Translated: cnbeta]