Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Intent to Ship: Push API

393 views
Skip to first unread message

Kit Cambridge

unread,
Aug 10, 2015, 8:24:04 PM8/10/15
to dev-pl...@lists.mozilla.org, pu...@mozilla.com
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/

Julien Wajsberg

unread,
Aug 11, 2015, 6:07:25 AM8/11/15
to dev-pl...@lists.mozilla.org
Le 11/08/2015 02:23, Kit Cambridge a écrit :
> 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.

This is exciting !
Can you share what the plan is for Fx/Android and Firefox OS ?

Thanks
--
Julien


signature.asc

Kit Cambridge

unread,
Aug 11, 2015, 5:35:18 PM8/11/15
to Julien Wajsberg, dev-pl...@lists.mozilla.org
There are a few outstanding bugs for Firefox OS. The implementation bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1151180, if you'd like to follow along. This will eventually replace the existing Simple Push API.

Unfortunately, we don't have a plan for Android yet. https://bugzilla.mozilla.org/show_bug.cgi?id=1191367 is a good one to watch; I'll send out an update as soon as we know more.

Martin Thomson

unread,
Aug 11, 2015, 5:36:23 PM8/11/15
to Julien Wajsberg, dev-platform
On Tue, Aug 11, 2015 at 3:07 AM, Julien Wajsberg <jwaj...@mozilla.com> wrote:
> Can you share what the plan is for Fx/Android and Firefox OS ?

Firefox OS can (and likely will) use the same basic technology, though
the UX story there is incomplete.

Fennec needs extra work in order to integrate with GCM (or Google Play
Services). We won't directly use our push service for Android because
we lose much of the advantage that push provides if we use a second
push service. That requires a fairly large amount of engineering
effort, I think, though see bug 1191367 for details. Fennec UX would
also need work.
0 new messages