Today, HTTP took a next major step towards becoming reality, it has been formally finalized and now is moving towards being completely standardized.
As per the blog published by IETF HTTP Working Group’s chairperson, Mark Nottingham, the standard was completed today and now it is on its way to the RFC Editor to move through the editorial processes before being circulated as a standard.
HTTP is a big deal; it’s an upcoming big version of the Hypertext Transfer Protocol, spot the largest change since 1999, when HTTP 1.1 was accepted.
The latest standard brings various benefits to one of Web’s major technologies, like longer-lived connections, speedier page loads, server push, and more items coming sooner. HTTP/2 utilizes the same HTTP APIs, which developers are familiar with, however, serves various new features they can accept.
One prominent change is, the requests for HTTP will be ‘cheaper ‘ to make. The Web community has frequently told developers to overlook too many HTTP requests to their pages that lead to optimization methods such as concatenation or code in line to lessen the requests. With HTTP/2 a brand new multiplexing feature, a lot of requests can be delivered at one point of time, so the page load is not blocked.
HTTP/2 also uses considerably fewer connections, hopefully impacting in lesser load for networks and servers. Google’s SPDY protocol was the base of new HTTP standard that is utilized by some technologies to control traffic that helps to develop security and latency, providing speedier page load times. Recently, Google released its plan to entirely shift to HTTP/2 in chrome.