W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

[push-api] Identifying registrations

From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 12 May 2014 16:08:09 -0700
Message-ID: <CABkgnnVVQOGxjkEskJ3U4tWTZTQEnd5OcVfWSyhAW=SGxz1d3Q@mail.gmail.com>
To: "public-webapps@w3.org" <public-webapps@w3.org>
Cc: EDUARDO FULLEA CARRERA <efc@tid.es>, bs3131@att.com, dougt@mozilla.com
The push API currently identifies a registration with a tuple:

interface PushRegistration {
    readonly    attribute DOMString pushEndpoint;
    readonly    attribute DOMString pushRegistrationId;

It looks like both are used by the push server.  Local methods seem to
rely on the pushRegistrationId; the remote application server uses the
pushEndpoint, though details are not currently specified [1].

In my experience, the pushEndpoint is a sufficiently unique
identifier.  Contingent on some conclusions on the protocol side, this
could be defined as a URL and used as an identifier.  That single
identifier should suffice.


p.s., the register() method on PushManager should be updated to return
Promise<PushRegistration> or Promise<DOMString> as appropriate.

[1] see webpush@ietf.org and related effort there
Received on Monday, 12 May 2014 23:08:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC