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

Push API draft uploaded

From: SULLIVAN, BRYAN L <bs3131@att.com>
Date: Thu, 24 May 2012 07:14:00 +0000
To: public-webapps <public-webapps@w3.org>
Message-ID: <59A39E87EA9F964A836299497B686C350FECF5C4@WABOTH9MSGUSR8D.ITServices.sbc.com>
Thanks to the inestimable help of the W3C staff I am now plugged into the mercurial mainline and have uploaded the first stab at the Push API
http://dvcs.w3.org/hg/push/raw-file/default/index.html

I incorporated Mozilla's client API ideas in https://wiki.mozilla.org/Services/Notifications/Push/API as the "PushManager" interface, and also in the "PushService" interface with some additions to support a more explicit event model for received message delivery, derived from Server-Sent Events.

A lot is still left unsaid, and I will work on examples.

I also have not addressed the server API aspect that Mozilla mentioned in their proposal. Like a lot that is left unsaid in their client API proposal (how does the browser determine what that magic server URL is...?), the server API is likely related to the specific Push service that is bound to the API. I am considering the use of Web Intents to discover and select the Push Service provider that the user wants apps to use, assuming that we can leave the "backend" details to the intent provider. I'm not yet sure how the pieces will fit together, how much needs to be defined, and how my earlier proposal about specific event source selection and filtering fits into this, but it's a start.

Thanks,
Bryan Sullivan
Received on Thursday, 24 May 2012 07:14:51 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:52 GMT