Platform/Features/SPDY: Difference between revisions
No edit summary |
mNo edit summary |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=SPDY | |Feature name=SPDY | ||
|Feature stage= | |Feature stage=Complete | ||
|Feature status= | |Feature status=Complete | ||
|Feature version=Firefox | |Feature version=Firefox 13 | ||
|Feature health= | |Feature health=OK | ||
|Feature status note= | |Feature status note=Shipped preffed off in 11. Preffed on for upcoming 13. | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
|Feature feature manager=Josh Aas | |Feature feature manager=Josh Aas | ||
|Feature lead engineer=Pat McManus | |Feature lead engineer=Pat McManus | ||
|Feature security lead=Curtis Koenig | |Feature security lead=Curtis Koenig | ||
|Feature qa lead=Ioana Budnar | |||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
Line 45: | Line 45: | ||
|Feature security health=OK | |Feature security health=OK | ||
|Feature security notes=[[Security/Reviews/Firefox10/SPDY|Notes]] | |Feature security notes=[[Security/Reviews/Firefox10/SPDY|Notes]] | ||
|Feature qa status=Signed off | |||
|Feature qa notes=[https://wiki.mozilla.org/index.php?title=Platform/Features/SPDY/TestPlan Test Plan] | |||
}} | }} |
Latest revision as of 18:56, 2 May 2012
Status
SPDY | |
Stage | Complete |
Status | Complete |
Release target | Firefox 13 |
Health | OK |
Status note | Shipped preffed off in 11. Preffed on for upcoming 13. |
Team
Product manager | ` |
Directly Responsible Individual | Josh Aas |
Lead engineer | Pat McManus |
Security lead | Curtis Koenig |
Privacy lead | ` |
Localization lead | ` |
Accessibility lead | ` |
QA lead | Ioana Budnar |
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 | sec-review-complete | Notes |
Privacy | ` | ` |
Localization | ` | ` |
Accessibility | ` | ` |
Quality assurance | Signed off | Test Plan |
User experience | ` | ` |
Product marketing | ` | ` |
Operations | ` | ` |