|Release target||Firefox 13|
|Status note||Shipped preffed off in 11. Preffed on for upcoming 13.|
|Directly Responsible Individual||Josh Aas|
|Lead engineer||Pat McManus|
|Security lead||Curtis Koenig|
|QA lead||Ioana Budnar|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
SPDY is a transport protocol designed as a successor to HTTP as part of Google's make the web faster initiative. It is currently supported in google chrome, on most google web services, in the contendo and strangeloopnetworks CDNs, and will be used by the amazon silk tablet browser.
2. Users & use cases
Users of high latency environments such as mobile should be improved page load times for pages with many resources.
Casual browsing will be more secure with respect to eavesdropping.
Servers should see reduced load.
Independent low latency traffic should see reduced queuing delays.
Because all of SPDY runs on SSL, having SSL False Start done would be helpful:
Also requires NPN support:
Interoperate with other spdy/2 implementations using high levels of concurrency.
SPDY over non-ssl.
Stage 2: Design
5. Functional specification
A SPDY implementation will wrap the existing HTTP implementation as a sort of in-browser proxy. This preserves all of the existing HTTP semantics and tools (e.g. firebug), while leveraging the on-the-wire benefits of SPDY.
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes
|Quality assurance||Signed off||Test Plan|