Sponsored Links
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.
There is emerging implementation experience and interest in a protocol that retains the semantics of HTTP without the legacy of HTTP/1.x message framing and syntax, which have been identified as hampering performance and encouraging misuse of the underlying transport.
The Working Group will produce a specification of a new expression of HTTP's current semantics in ordered, bi-directional streams. As with HTTP/1.x, the primary target transport is TCP, but it should be possible to use other transports.
Work will begin using draft-mbelshe-httpbis-spdy-00 as a starting point; proposals are to be expressed in terms of changes to that document. Note that consensus is required both for changes to the document and anything that remains in the document. In particular, because something is in the initial document does not imply that there is consensus around the feature or how it is specified. The deliverable of the WG is HTTP/2.0, and there is no consideration of preserving backwards compatibility with the initial starting point.
As part of the HTTP/2.0 work, the following issues are explicitly called out for
consideration:
* A negotiation mechanism that is capable of not only choosing between
HTTP/1.x and HTTP/2.x, but also for bindings of HTTP URLs to other
transports (for example).
* Header compression (which may encompass header encoding or tokenisation)
* Server push (which may encompass pull or other techniques)
Source from For more info visit :-https://http2.github.io/
Sponsored
No comments: