Skip to main content
To Customer Support To Customer Support

HTTP/2 should be a faster, more efficient Web protocol.

by Peter Bright - Feb 18, 2015

 

The Internet Engineering Task Force's HTTP Working Group has finalized its work on Hypertext Transfer Protocol 2, the successor to the HTTP/1.0 and HTTP/1.1 protocols that are the core of the Web.

The working group has actually finalized two closely related specifications. The first is HTTP/2 itself. The second is called HPACK, a specification for compressing HTTP/2 headers.

Work on HTTP/2 began in 2012 in response to the development of Google's SPDY protocol. Google created SPDY to address a number of performance gripes that the company had with traditional HTTP.

 

Full Article
The following article is a update:

************************************

HTTP/2: The future of the Web demystified

By Serdar Yegulalp

 

http://images.techhive.com/images/article/2015/01/dev-tools_5-100540335-primary.idge.jpg Credit: Shutterstock

Making the most of HTTP/2 will take a lot of work on the part of Web designers, IT admins, and server jockeys. Here's what to expect

 

 

Out with the old, in with the new, as the saying goes -- but when it comes to an overhaul of one of the Internet’s most fundamental protocols, what exactly is coming in with the new?

HTTP has done yeoman’s work shouldering the explosive growth of Web traffic since it was first devised. But the truth is HTTP was conceived at a time when the amount of traffic one could expect to get to a given Web server was minimal and sparse. Over time, a real need has arisen to rethink how the Web itself is put together to serve everyone better.

 

full article

Reply


Terms & Conditions