Platform/Features/Websockets: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 45: Line 45:
== Goals/Use Cases ==
== Goals/Use Cases ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.
== Security ==
[[Security/Reviews/Firefox6/ReviewNotes/WebSockets|Security Notes]]


== Non-Goals ==
== Non-Goals ==

Revision as of 17:31, 15 June 2011

Feature Status ETA Owner
Websockets Waiting on Review (Josh Aas) Unknown Pat McManus

Summary

This feature adds support for Websockets to Firefox, as defined by the IETF working group.

Team

Who's working on this?

  • Lead Developer: Pat McManus
  • Product Manager: Chris Blizzard
  • QA: Unknown
  • Security: Curtis Koenig

Pat's the lead on this, both in terms of code but also in the IETF working group as well.

Release Requirements

We should have support for the full Websockets API, based on the last version of the draft that makes major on-the-wire protocol changes. It should also have full tests and undergone interoperability testing.

Next Steps

Protocol -07 is about done, and working group is in last call. There are some API things that still need doing, but the protocol bits should be about done, which means we can land.

Related Bugs & Dependencies

WebSockets - upgrade to ietf-06+

Designs

Any and all mockups, design specs, tech specs, etc. Either inline or linked to.

Goals/Use Cases

The high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.

Security

Security Notes

Non-Goals

Things we are specifically not doing or building as part of this feature.

Other Documentation

Can include things like:

  • Competitive landscape
  • Research & references
  • Whatever else is useful to the project.

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked, but not yet at risk of missing this release.
  At Risk: feature is at risk of missing this release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.


Please remove this line and any non-relevant categories below. Add whatever other categories you feel are appropriate.