1013251 - [meta] Make the Loop Push Handler more robust

Status: RESOLVED DUPLICATE of bug 1002414

(Hello (Loop) :: Client, defect, P2)

Description

[Mark Banner (:standard8)]

Currently the push handler is deficient in multiple ways:

- If initial connection fails, it doesn't handle re-connect attempts.
- It doesn't handle network disconnects (aka auto-reconnect).
- It only implements a small subset of the push notification protocol.

There's possible way forwards:

- See if we can use a subset of the push notification handling from the main push service, even though it isn't enabled in desktop yet (this would probably mean running on main thread rather than a service worker).

- If we can't use that, then we need to harden up our existing push handler, which probably includes:
-- Fixing the above mentioned issues
-- Reviewing the push client - server API and ensure that we meet the parts that we need to (https://wiki.mozilla.org/WebAPI/SimplePush/Protocol)

Comment 1

[Dan Mosedale (:dmosedale, :dmose)]

My understanding is that at some point, SimplePush is intended to be replaced by the "Services Channel".  Since we're not using official push code, we presumably need to figure out how to keep abreast of that work so that it doesn't change out from under us at some point.

Comment 2

[Ben Bangert [:benbangert]]

Just an FYI, Services Channel is just a transport, which SimplePush will transition to using, it won't be replacing it. It should make it faster to implement the proposed WebPush spec as well (which can deliver data in the payload).

Comment 3

[Maire Reavy [:mreavy]]

Mark -- can you sanity-check the bug breakdown for this?

Comment 4

[Mark Banner (:standard8)]

No longer need this, bug 1002414 will do the only work that's necessary.