Platform/Features/SPDY: Difference between revisions

Revision as of 16:32, 3 October 2011

Please use "Edit with form" above to edit this page.

Status

SPDY
Stage	Development
Status	In progress
Release target	`
Health	OK
Status note	Working on design and early prototypes

Team

Product manager	Chris Blizzard
Directly Responsible Individual	Josh Aas
Lead engineer	Pat McManus
Security lead	Curtis Koenig
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	`
UX lead	`
Product marketing lead	`
Operations lead	`
Additional members	`

Open issues/risks

`

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.

3. Dependencies

Because all of SPDY runs on SSL, having SSL False Start done would be helpful:

https://bugzilla.mozilla.org/show_bug.cgi?id=658222

Also requires NPN support:

https://bugzilla.mozilla.org/show_bug.cgi?id=547312

4. Requirements

Interoperate with other spdy/2 implementations using high levels of concurrency.

Non-goals

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

https://bugzilla.mozilla.org/show_bug.cgi?id=528288

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

`

Feature details

Priority	P1
Rank	999
Theme / Goal	`
Roadmap	Platform
Secondary roadmap	`
Feature list	Platform
Project	Responsiveness
Engineering team	Networking

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	`
Product marketing	`	`
Operations	`	`

@@ Line 13: / Line 13: @@
 }}
 {{FeaturePageBody
-|Feature dependencies=Requires that we have SSL False Start done.
+|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.
+|Feature users and 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.
+|Feature dependencies=Because all of SPDY runs on SSL, having SSL False Start done would be helpful:
 https://bugzilla.mozilla.org/show_bug.cgi?id=658222
@@ Line 20: / Line 28: @@
 https://bugzilla.mozilla.org/show_bug.cgi?id=547312
+|Feature requirements=Interoperate with other spdy/2 implementations using high levels of concurrency.
+|Feature non-goals=SPDY over non-ssl.
+|Feature functional spec=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.
 |Feature implementation plan=https://bugzilla.mozilla.org/show_bug.cgi?id=528288
 }}