P/2 Approved

welcome to http://www.startdays.com
welcome to http://www.ijachouf.com
welcome to http://www.swtools.biz
welcome to http://www.decoderhd.com

[29]HTTP/2 Approved

dim, nov 29, 2015

[30]Flash News, [31]Technology

HTTP/2

This is the home page for HTTP/2, a major revision of the Web's
protocol. It is maintained by the [32]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 [33]SPDY, but HTTP/2 has evolved to take the
community's input into account, incorporating several improvements in
the process.

See [34]our charter for more details of the scope of the work, as well
as our [35]Frequently Asked Questions.

Specifications

HTTP/2 is comprised of two specifications:
* Hypertext Transfer Protocol version 2 – [36]RFC7540
* HPACK – Header Compression for HTTP/2 – [37]RFC7541

Implementations

We track [38]known implementations of HTTP/2 on our wiki.



After more than two years of discussion, over [39]200 design
issues, [40]17 drafts, and [41]30 implementations, the HTTP/2 and HPACK
specifications have now been approved by the IETF's steering group for
publication as standards-track RFCs. The result is that HTTP/2 will
help provide faster user experience for browsing, reduce the amount of
bandwidth required, and make the use of secure connections easier.

The [42]HTTP Working Group began work on HTTP/2 in 2012 by selecting
Google's SPDY protocol as the starting point, holding a series of six
interim meetings to incorporate community feedback. This resulted in
substantial changes to the format of the protocol, its compression
scheme, and its mapping to the semantics of HTTP.

The resulting protocol is designed to allow a seamless switch
between HTTP/1 and HTTP/2, with minimal changes to applications and
APIs, while at the same time offering improved performance and better
use of network resources. Web users largely will be able to benefit
---------------------------------------------------------------
---------------------------------------------------------------
---------------------------------------------------------------