Hi folks,
On Wed, Mar 2, 2016 at 10:06 AM, Nicholas Alexander
wrote:
> Summary: "The Push API gives web applications the ability to receive
> messages pushed to them from a server, whether or not the web app is in the
> foreground, or even currently loaded, on a user agent. This lets developers
On Thu, Mar 3, 2016 at 11:21 AM, Valentin Gosu
wrote:
> Does that mean that the service worker's endpoint will be on GCM? Or that
> the Mozilla push endpoint will notify GCM to wake up Firefox on Android?
>
A consuming SW in Firefox for Android will see a Web Push endpoint
indistinguishable from
Does that mean that the service worker's endpoint will be on GCM? Or that
the Mozilla push endpoint will notify GCM to wake up Firefox on Android?
On 3 March 2016 at 04:44, Mark Finkle wrote:
> Firefox on Android is not using the polling technique used on Desktop. We
> are hooking into Google's
Firefox on Android is not using the polling technique used on Desktop. We
are hooking into Google's Cloud Messaging (GCM) system. The Android system
will notify Firefox of incoming pings.
On Wed, Mar 2, 2016 at 1:16 PM, Ben Bucksch wrote:
> The poller is only running while Firefox is running, co
This is great.
As I said elsewhere, I don't think that we can pref this on until bug
1252650 lands. It turns out that "gecko not running" is pretty much
the only interesting state for push.
On Thu, Mar 3, 2016 at 5:06 AM, Nicholas Alexander
wrote:
> Summary: "The Push API gives web applications
The poller is only running while Firefox is running, correct?
(I hope so. I wouldn't want FF to stay resident after I closed it.)
___
mobile-firefox-dev mailing list
mobile-firefox-dev@mozilla.org
https://mail.mozilla.org/listinfo/mobile-firefox-dev
6 matches
Mail list logo
