Lines Matching full:spdy
11 SPDY Protocol
12 draft-mbelshe-httpbis-spdy-00
16 This document describes SPDY, a protocol designed for low-latency
17 transport of content over the World Wide Web. SPDY introduces two
58 Internet-Draft SPDY Feb 2012
72 2. SPDY Framing Layer . . . . . . . . . . . . . . . . . . . . . . 6
100 3. HTTP Layering over SPDY . . . . . . . . . . . . . . . . . . . 33
115 Internet-Draft SPDY Feb 2012
130 5.2. HTTP Headers and SPDY Headers . . . . . . . . . . . . . . 43
136 7. Incompatibilities with SPDY draft #2 . . . . . . . . . . . . . 45
172 Internet-Draft SPDY Feb 2012
186 SPDY adds a framing layer for multiplexing multiple, concurrent
190 can work over SPDY with little or no change on behalf of the web
193 The SPDY session offers four improvements over HTTP:
196 that can be issued concurrently over a single SPDY connection.
210 SPDY attempts to preserve the existing semantics of HTTP. All
212 negotiations, etc work as they do with HTTP; SPDY only replaces the
217 The SPDY Specification is split into two parts: a framing layer
229 Internet-Draft SPDY Feb 2012
237 client: The endpoint initiating the SPDY session.
243 frame: A header-prefixed sequence of bytes sent over a SPDY
246 server: The endpoint which did not initiate the SPDY session.
250 session error: An error on the SPDY session.
253 within a SPDY session.
255 stream error: An error on an individual SPDY stream.
286 Internet-Draft SPDY Feb 2012
289 2. SPDY Framing Layer
293 The SPDY framing layer (or "session") runs atop a reliable transport
295 initiator. SPDY connections are persistent connections.
321 network byte order. SPDY does not enforce alignment of types in
343 Internet-Draft SPDY Feb 2012
346 Version: The version number of the SPDY protocol. This document
347 describes SPDY version 3.
400 Internet-Draft SPDY Feb 2012
423 All SPDY endpoints MUST accept compressed data frames.
427 use application level compression rather than SPDY stream level
430 Each SPDY
457 Internet-Draft SPDY Feb 2012
462 SPDY defines 3 control frames to manage the lifecycle of a stream:
514 Internet-Draft SPDY Feb 2012
571 Internet-Draft SPDY Feb 2012
602 The SPDY framing layer has only two types of errors, and they are
628 Internet-Draft SPDY Feb 2012
651 loops. Sending a RST_STREAM does not cause the SPDY session to be
662 Because TCP provides a single stream of data on which SPDY
685 Internet-Draft SPDY Feb 2012
742 Internet-Draft SPDY Feb 2012
799 Internet-Draft SPDY Feb 2012
856 Internet-Draft SPDY Feb 2012
863 does not support the SPDY version requested.
905 by the client across SPDY sessions and returned to the server in
913 Internet-Draft SPDY Feb 2012
937 Version: The SPDY version number.
970 Internet-Draft SPDY Feb 2012
1027 Internet-Draft SPDY Feb 2012
1073 Version: The SPDY version number.
1084 Internet-Draft SPDY Feb 2012
1141 Internet-Draft SPDY Feb 2012
1156 Version: The SPDY version number.
1198 Internet-Draft SPDY Feb 2012
1238 control in SPDY. Flow control in SPDY is per hop, that is, only
1239 between the two endpoints of a SPDY connection. If there are one or
1255 Internet-Draft SPDY Feb 2012
1258 Flow control in SPDY is implemented by a data transfer window kept by
1285 Version: The SPDY version number.
1305 When a SPDY connection is first established, the default initial
1312 Internet-Draft SPDY Feb 2012
1359 client certificates to the server. A SPDY client may decide to send
1360 requests for resources from different origins on the same SPDY
1369 Internet-Draft SPDY Feb 2012
1378 associated with a SPDY session. When the client needs to send a
1395 SPDY given the multiplexed nature of SPDY. Specifically, imagine
1426 Internet-Draft SPDY Feb 2012
1442 SPDY certificate proof" using the empty string as context. ForRSA
1459 resend the request. Note, SPDY does not allow the server to request
1483 Internet-Draft SPDY Feb 2012
1506 exceed 2^24, as that is the maximum size of a SPDY frame.
1512 exceed 2^24, as that is the maximum size of a SPDY frame.
1540 Internet-Draft SPDY Feb 2012
1597 Internet-Draft SPDY Feb 2012
1654 Internet-Draft SPDY Feb 2012
1711 Internet-Draft SPDY Feb 2012
1768 Internet-Draft SPDY Feb 2012
1773 in one direction on a connection. SPDY uses a SYNC_FLUSH between
1825 Internet-Draft SPDY Feb 2012
1828 3. HTTP Layering over SPDY
1830 SPDY is intended to be as compatible as possible with current web-
1841 Clients SHOULD NOT open more than one SPDY session to a given origin
1844 Note that it is possible for one SPDY session to be finishing (e.g. a
1846 while another SPDY session is starting.
1850 SPDY provides a GOAWAY message which can be used when closing a
1860 finish. The client will be able to determine this because SPDY
1871 If a SPDY client closes the connection, it should also send a GOAWAY
1882 Internet-Draft SPDY Feb 2012
1902 in SPDY is mostly unchanged from today's HTTP header block, with the
1939 Internet-Draft SPDY Feb 2012
1956 early versions of SPDY that failure to send a content length
1996 Internet-Draft SPDY Feb 2012
2033 Stateless Authentication over SPDY is identical to how it is
2034 performed over HTTP. If multiple SPDY streams are concurrently sent
2044 is problematic in SPDY because it makes it impossible for a client to
2053 Internet-Draft SPDY Feb 2012
2056 To deal with this case, SPDY servers using Stateful Authentication
2075 SPDY enables a server to send multiple replies to a client for a
2088 policy. For example, a SPDY connection to www.foo.com is generally
2097 headers associated with them. At the framing layer, SPDY pushed
2110 Internet-Draft SPDY Feb 2012
2167 Internet-Draft SPDY Feb 2012
2224 Internet-Draft SPDY Feb 2012
2229 Authors' notes: The notes in this section have no bearing on the SPDY
2248 reuse the SPDY framing layer is a non goal.
2252 Error handling at the SPDY layer splits errors into two groups: Those
2253 that affect an individual SPDY stream, and those that do not.
2256 in tact, SPDY attempts to use the RST_STREAM as a mechanism to
2260 For errors occuring outside of a single stream context, SPDY assumes
2266 SPDY attempts to use fewer connections than other protocols have
2274 packets sent by SPDY can be as much as 40% less than HTTP. Handling
2281 Internet-Draft SPDY Feb 2012
2285 become a scalability problem, and SPDY reduces this load.
2288 Because SPDY multiplexes multiple, independent streams onto a single
2296 SPDY favors use of fixed length 32bit fields in cases where smaller,
2298 like a tragic waste of bandwidth. SPDY choses the simple encoding
2301 The goal of SPDY is to reduce latency on the network. The overhead
2302 of SPDY frames is generally quite low. Each data frame is only an 8
2311 addressing other aspects of SPDY and TCP interactions, we believe
2338 Internet-Draft SPDY Feb 2012
2343 are using two different origins over a single SPDY session, we simply
2364 already compressed. Because of this, SPDY does allow data
2368 at the SPDY layer, site administrators could simply force compression
2395 Internet-Draft SPDY Feb 2012
2405 5.2. HTTP Headers and SPDY Headers
2408 Because SPDY merges the existing HTTP headers with SPDY headers,
2411 introduced for layering HTTP over SPDY are prefixed with ":". ":" is
2417 By utilizing TLS, we believe that SPDY introduces no new cross-
2452 Internet-Draft SPDY Feb 2012
2459 SPDY aims to keep connections open longer between clients and servers
2470 The SPDY SETTINGS frame allows servers to store out-of-band
2509 Internet-Draft SPDY Feb 2012
2512 7. Incompatibilities with SPDY draft #2
2566 Internet-Draft SPDY Feb 2012
2623 Internet-Draft SPDY Feb 2012
2629 SPDY: Adam Langley, Wan-Teh Chang, Jim Morrison, Mark Nottingham,
2680 Internet-Draft SPDY Feb 2012
2737 Internet-Draft SPDY Feb 2012
2742 Derive SPDY's Initial Dictionary for Zlib Compression",
2744 SPDY-Fan.pdf>.
2794 Internet-Draft SPDY Feb 2012
2851 Internet-Draft SPDY Feb 2012
