canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,776
edits
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== Introduce Feature (5-10 minutes) == | == Introduce Feature (5-10 minutes) == | ||
:: https://wiki.mozilla.org/Security/Reviews/CrossOriginEventSource | :: https://wiki.mozilla.org/Security/Reviews/CrossOriginEventSource | ||
=== Goal of Feature, what is trying to be achieved (problem solved, use cases, etc) === | === Goal of Feature, what is trying to be achieved (problem solved, use cases, etc) === | ||
Push-based event triggers, based on CORS/XHR stuff. Syntax sugar to make push and event notifications easier and require less scripting support for connection maintenance, etc. | Push-based event triggers, based on CORS/XHR stuff. Syntax sugar to make push and event notifications easier and require less scripting support for connection maintenance, etc. | ||
We already have support for Server Sent DOM Events. This was done in {{bug|338583}} and security review happened in [[Security/Reviews/Firefox6/ReviewNotes/ServerDomEvents|ServerDomEvents]] | |||
The goal of this feature is to allow cross-site pushing of server sent events. For example allowing a bank site to push events that keep you up-to-date with your portfolio, or facebook pushing an event stream containing updates to your wall. http://pulse.mozilla.org/ has also expressed desire to use this to allow other sites to consume and visualize data concerning the mozilla project. | The goal of this feature is to allow cross-site pushing of server sent events. For example allowing a bank site to push events that keep you up-to-date with your portfolio, or facebook pushing an event stream containing updates to your wall. http://pulse.mozilla.org/ has also expressed desire to use this to allow other sites to consume and visualize data concerning the mozilla project. | ||