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

Re: Push API draft uploaded

From: JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>
Date: Fri, 25 May 2012 13:36:26 +0200
To: "SULLIVAN, BRYAN L" <bs3131@att.com>, public-webapps <public-webapps@w3.org>
Message-id: <CBE5397D.2E7B3%jmcf@tid.es>
I have some comments:

I think the idea is to decouple permissions from APIs, making that part of
a Security Model, so I don't understand why we are putting here that
functionality.

Concerning wakeup, etc. I think that should not be part of the API itself
but of the App Manifest

I think we need to distinguish between registering the interest on
receiving push messages and receiving push messages themselves.

The current API does not address the possibility of having a queue of
pending messages.

best

El 24/05/12 09:14, "SULLIVAN, BRYAN L" <bs3131@att.com> escribió:

>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
>
>
>
>



Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Received on Friday, 25 May 2012 11:38:29 GMT

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