Re: Push API draft uploaded

[JOSE MANUEL CANTERA FONSECA]

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 bs3...@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

Re: [DRAFT] Web Intents Task Force Charter

[JOSE MANUEL CANTERA FONSECA]

Hi Robin,

Thanks for setting this up.

My understanding is that intents could be used as a mechanism that will
allow the web browser to talk to other apps on the device, and those apps
can  be web or native ... From your description it seems it is only web
app to web app communication ...

best

El 10/11/11 14:54, Robin Berjon ro...@berjon.com escribió:

Hi all,

here is a draft of the Intents joint Task Force charter for comments from
WebApps and Device APIs. A TF charter is nothing formal and requires no
overhead ‹ it can live as an email in a mailing list, it just documents
the existence of the TF, and gives a few indications as to how it works.

I've added some notes below about the points that may be contentious. If
no one screams bloody murder by Monday I'll ask the Team to set things
up. It's short but we've discussed this together last week, and DAP
intends (no pun, err, intended) to rely rather heavily on Intents so we'd
rather move fast rather than wait for WebApps to recharter, which could
take a few months.



The Web Intents Task Force works on a joint deliverable of the WebApps
and Device APIs WGs that aims to produce a way for web applications to
register themselves as handlers for services, and for other web
applications to interact with these through simple requests brokered by
the user agent (a system commonly known as Intents, or Activities).

The mailing list on which the TF's discussions take place is
public-inte...@w3.org. The chair is Robin Berjon.

Operational modalities such as whether or not to have phone and/or face
to face meetings, as well as where to store the draft document are left
to the TF to decide for itself. Decisions are made by consensus inside of
the task force and do not require separate ratification by the wider
groups.

It is important to note that until such a time as the WebApps WG is
rechartered with Intents in its list of deliverables, it will be
necessary for participants in WebApps who are not in Device APIs and wish
to make substantive contributions (just joining the discussion and
providing comments is always fine) to make an RF commitment for this
deliverable (not necessarily for other DAP deliverables, naturally). For
more details on this, please contact the W3C Team.



ISSUES:
  € The description isn't terribly precise, but I think it works

  € As I've said before, I am only putting myself forward as chair
because so far no one else stepped up. I don't mind doing it, but I
equally don't mind letting someone else do it. I don't expect it to be a
very demanding position.

WDYT?

--
Robin Berjon - http://berjon.com/ - @robinberjon




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