W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2014

Push API and Service Workers

From: Shijun Sun <shijuns@microsoft.com>
Date: Wed, 15 Oct 2014 21:42:05 +0000
To: public-webapps <public-webapps@w3.org>
Message-ID: <b36412f36d144e2ba0b838236b1c4b7d@BLUPR03MB405.namprd03.prod.outlook.com>

I'm with the IE Platform team at Microsoft.  I joined the WebApps WG very recently.  I am looking into the Push API spec, and got some questions.  Hope to get help from experts in the WG.

The current API definition is based on an extension of the Service Workers.  I'd like to understand whether the Service Workers is a must-have dependency for all scenarios.  It seems some basic scenarios can be enabled without the Service Worker if the website can directly create a PushRegistrationManager.  I'm looking at Fig. 1 in the spec.  If the user agent can be the broker between the "Push client" and the webpage, it seems some generic actions can be defined without the Service Workers - for example immediately display a toast notification with the push message.

It is very likely I have missed some basic design principle behind the current API design.  It'd be great if someone could share insights on the scenarios and the normative dependency on the Service Workers.

All the Best, Shijun
Received on Wednesday, 15 October 2014 21:42:36 UTC

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