1. SPDY
Reducing web page load latency and
improve web security
Edited by Oded Rotter
oded1233@gmail.com
Based On:
http://en.wikipedia.org/wiki/SPDY
http://dev.chromium.org/spdy/spdy-whitepaper
http://www.scribd.com/doc/51606190/SPDY-PROTOCOL-ppt

2. What is SPDY ?
An experimental networking protocol developed
primarily at Google for transporting web content
has reference implementations.
Available in Chrome & Firefox.
SPDY achieves reduced latency through
compression, multiplexing, and prioritization
SPDY does not replace HTTP
(modifies the way HTTP requests and responses are sent over the wire)
The IETF working group for HTTPbis is planning to
start working on HTTP 2.0 with SPDY as one of the
candidates for a starting point.

3. And …?
• Only one TCP connection per client is required
(Http pipline has some issues which is solved here)
• For utilizing https ,TLS extension Next Protocol
Negotiation (NPN) is used
• Transmissions are gzip or Deflate compressed by
design (in contrast to HTTP, where the headers are
not compressed).
• Servers may hint or even push content instead of
awaiting individual requests for each resource of a
web page.
• Prioritizing is done by the client

4. Server side story
• On the server side ,all you need to do is put SPDY-
compatible translation layer
• When sent over SPDY, HTTP requests are
processed, tokenized, simplified and compressed.
• Each SPDY endpoint keeps track of which headers
have been sent in the past requests and can avoid
resending the headers that have not changed;
those that must be sent are sent compressed.