HTTP/2 Gets One Step Closer to Standardization, Currently in Editorial Process
HTTP is finally evolving as some major changes are being made to it. These changes are finalized and will soon be standardized according to a blog post by Mark Nottingham, who currently chairs the IETF HTTP Working Group.
He revealed that the standard is complete and is handed to the RFC Editor for editorial process, after that it will be published for public use. Nottingham stated:
The IESG has formally approved the HTTP/2 and HPACK specifications, and they’re on their way to the RFC Editor, where they’ll soon be assigned RFC numbers, go through some editorial processes, and be published.
HTTP/2 is a successor of Hypertext Transfer Protocol, and is the biggest change in 16 years. HTTP 1.1 was standardized way back in 1999 and since then, no major change has been made to the protocol.
The new version will introduce a number changes and benefits as page loading times will be reduced, longer-lived connections, data packets will arrive much sooner in addition to server push. HTTP/2 is working on the same APIs as HTTP, developers are familiar with this and it offers many new benefits as well.
The new standard will also address an issue developers have faced for a long time, multiple HTTP requests. These put a lot of strain on servers but users should rest assured that it will now be cheaper to make these requests. This will have an impact on page loading and users should notice faster loading times.
HTTPS/2 will use multiplexing, a process in which multiple requests are sent at the same time, so loading isn’t blocked. It also uses fewer connections compared to HTTP, meaning load on networks and servers will be reduced. Nottingham noted in one of his previous posts:
HTTP/2 is designed to use fewer connections, so servers and networks will enjoy less load. This is especially important when the network is getting congested, because HTTP/1’s use of multiple connections for parallelism adds to the problem.
On the other hand, the “server push” feature will enable server to send data to the “client’s cache for future use.” Moreover, HTTP/2 doesn’t require the use of TLS but its better performance will make the use of encryption much easier.
For more on HTTP/2 visit the official blog.