Firefox3.1/Server-Sent DOM Events
Overview
Add support for WhatWG's Server-Sent DOM Events HTML5.
- Background links
- bug 338583 - Add support for Server-Sent DOM Events (Remote Events)
- http://www.whatwg.org/specs/web-apps/current-work/#server-sent-events - HTML5 spec for Server-sent events
Security and Privacy
- What security issues do you address in your project?
- Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.
Exported APIs
- Please provide a table of exported interfaces (APIs, ABIs, protocols, UI, etc.)
- Explain the significant file formats, names, syntax, and semantics.
- Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully?
- Does it change any existing interfaces?
Module interactions
- What other modules are used (REQUIRES in the makefile, interfaces)
Data
- What data is read or parsed by this feature
- What is the output of this feature
- What storage formats are used
Reliability
- What failure modes or decision points are presented to the user?
- Failures are redirected to CSS system through the normal parsing mechanisms.
- Can its files be corrupted by failures? Does it clean up any locks/files after crashes?
- No files to corrupt.
Configuration
- Can the end user configure settings, via a UI or about:config? Hidden prefs? Environment variables?
- No.
- Are there build options for developers? [#ifdefs, ac_add_options, etc.]
- No.
- What are its on-going maintenance requirements (e.g. Web links, perishable data files)?
- None.
Relationships to other projects
Are there related projects in the community? No.