Changes between Version 2 and Version 3 of Http2Proposals


Ignore:
Timestamp:
Apr 26, 2012, 10:05:56 PM (8 years ago)
Author:
mnot@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Http2Proposals

    v2 v3  
    99== Current Proposals ==
    1010
     11=== [http://tools.ietf.org/html/draft-mbelshe-httpbis-spdy SPDY] ===
     12
     13   This document describes SPDY, a protocol designed for low-latency
     14   transport of content over the World Wide Web. SPDY introduces two
     15   layers of protocol.  The lower layer is a general purpose framing
     16   layer which can be used atop a reliable transport (likely TCP) for
     17   multiplexed, prioritized, and compressed data communication of many
     18   concurrent streams.  The upper layer of the protocol provides HTTP-
     19   like RFC2616 semantics for compatibility with existing HTTP
     20   application servers.
     21
     22=== [http://tools.ietf.org/html/draft-montenegro-httpbis-speed-mobility HTTP Speed + Mobility] ===
     23
     24   This document describes "HTTP Speed+Mobility," a proposal for HTTP
     25   2.0 that emphasizes performance improvements and security while at
     26   the same time accounting for the important needs of mobile devices
     27   and applications.  The proposal starts from both the Google SPDY
     28   protocol and the work the IETF has done around !WebSockets.  The
     29   proposal is not a final product but rather is intended to form a
     30   baseline for working group discussion.
     31
     32=== [http://tools.ietf.org/html/draft-tarreau-httpbis-network-friendly Network-Friendly HTTP Upgrade] ===
     33
     34   This document proposes an upgrade to HTTP messaging which aims at
     35   being faster, more robust and more friendly to mobile networks than
     36   the current version, while retaining the same semantics and offering
     37   a high enough compatibility level to make it possible to implement
     38   highly efficient gateways between existing implementations and this
     39   presently described version, thus offering a smooth upgrade path for
     40   legacy applications.