Hi, As of Firefox 42 (Desktop only), the Push API [1] will be turned on by default. This API allows an active service worker to receive server-sent push messages in the background. The worker can then show a notification to the user, or perform updates.
Push has been developed behind the `dom.push.enabled` preference [2], and previously announced in this "intent to implement" thread: https://groups.google.com/d/msg/mozilla.dev.platform/bO3zwfACypQ/akAU1ZQhqt8J. Since Push requires service workers, Firefox 42 will also ship with the `dom.serviceWorkers.enabled` pref turned on. Pending further discussion around the preferred cryptographic curve for message encryption, Push in 42 will not support data delivery. Sites that are granted permission to show notifications can receive push messages. Each service worker can only receive a limited number of messages without requiring the user to visit the site again. If a site sends excessive background push messages, its subscription will be dropped, and restored on the next visit. Google has shipped an implementation in Chrome 42 [3], also without data. Some additions to the existing interfaces are anticipated, based on implementer and user feedback. We also expect to tune the quota policy and permission model. The Mozilla Push server [4] manages subscription state and handles message delivery. The server does not require registration; any site with push permissions can create subscriptions and send messages. Please let me know if you have questions or concerns. Thanks, - kit [1]: https://w3c.github.io/push-api/ [2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1153499 [3]: https://groups.google.com/a/chromium.org/d/msg/blink-dev/UdGlL9PtBLo/HOZZ4sjV-QkJ [4]: https://autopush.readthedocs.org/en/latest/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
