Madrid, 7 april, 2015.- Mark Nottingham, Chair the IETF HTTP Working Group and am a member of the W3C TAG (Usually write here about the Web, protocol design, HTTP, and caching) announced a few weeks ago: “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”.
IETF HTTP Working Group: What is HTTP/2?
HTTP/2 is a replacement for how HTTP is expressed “on the wire.” It is not a ground-up rewrite of the protocol; HTTP methods, status codes and semantics are the same, and it should be possible to use the same APIs as HTTP/1.x (possibly with some small additions) to represent the protocol.
The focus of the protocol is on performance; specifically, end-user perceived latency, network and server resource usage. One major goal is to allow the use of a single connection from browsers to a Web site.
The basis of the work was SPDY, but HTTP/2 has evolved to take the community’s input into account, incorporating several improvements in the process.
HTTP/2 is comprised of two specifications:
- Hypertext Transfer Protocol version 2 – current IETF draft, editors’ copy
- HPACK – Header Compression for HTTP/2 – current IETF draft, editors’ copy
We track known implementations of HTTP/2 on our wiki.
Advantages of the new web protocol
According to the web portal hypertextual, the advantages of HTTP 2 are the following:
- The reason to develop this new protocol of the limitations of the past. Today with the above specifications, if too many connection requests to a server using degrades performance and increases the response time.
- The implementation of HTTP / 2 will increase the number of requests permitidasPor this, the arrival of HTTP / 2, when reviewing the protocol transfer most important hypertext since 1999 (when HTTP 1.1 was adopted.), Involves a number of benefits very interesting for the web. As Google said, is a binary protocol and multiplex, which can be used in parallel and independently of the number of requests. Also use header compression to reduce the overhead for requests and allows servers to do “push” the client proactively memory caches. Therefore faster, withstands more simultaneous requests and has a greater ease of implementation.
- However, one of the most interesting benefits of the arrival of HTTP / 2 it will be much easier to implement, since as mentioned above, the multiplex characteristics of this new protocol allow a greater number of web applications generate more responses for each request at the same time, so the load does not affect the web that it can be blocked or not.
By the way, Wikipedia, in its definition of HTTP2, provides the following links to document this new reality:
- Hypertext Transfer Protocol Bis (httpbis) – Charter. IETF. 2012.
- SPDY: Microsoft and Google battle over the future of HTTP/2
- Can the rise of SPDY threaten HTTP?». Restlet. 2011.
- Sebastian Anthony (28 de marzo de 2012). «S&M vs. SPDY:
- Microsoft and Google battle over the future of HTTP/2». ExtremeTech.
- Proposal for a Network-Friendly HTTP Upgrade, March 29, 2012
HTTP2 Expression of Interest, Doug Beaver, 15 Jul 2012
- Dio Synodinos (30-11-2012). «HTTP/2 First Draft Published». InfoQ.
- Final HTTP-NG Activity Statement». World Wide Web Consortium.