W3C home > Mailing lists > Public > public-sysapps@w3.org > June 2012

RE: Updated charter proposal

From: SULLIVAN, BRYAN L <bs3131@att.com>
Date: Mon, 4 Jun 2012 16:53:27 +0000
To: Mounir Lamouri <mounir@lamouri.fr>, "public-sysapps@w3.org" <public-sysapps@w3.org>
Message-ID: <59A39E87EA9F964A836299497B686C350FEECA31@WABOTH9MSGUSR8D.ITServices.sbc.com>
Comments inline.

Bryan Sullivan 

-----Original Message-----
From: Mounir Lamouri [mailto:mounir@lamouri.fr] 
Sent: Monday, June 04, 2012 6:38 AM
To: public-sysapps@w3.org
Subject: Re: Updated charter proposal

On 06/03/2012 11:19 AM, Adam Barth wrote:
> Hi SysApps,
> Based on the discussion on this list, I've put together an updated
> proposal for a charter:
> http://abarth.github.com/websec/drafts/sysapps-charter.html

When working on the Alarm API and other APIs (like Push Notification
API), Jonas and I realized that we probably need an API that would start
web apps when needed. For example, with the Alarm API, to make sure an
alarm isn't missed, the app should be started when the application isn't
running; with Web Intents, we might need something similar when the user
picks an application that isn't running yet.
It appears that using DOM events for that isn't working very well
because the developer will have to know when the event will be sent
during the startup process which isn't easy to define.

More information about this API here:

<bryan> As noted in discussion of the Push API on Webapps, this seems a useful capability and could address the generic app wakeup (and incoming event dispatching) needs such as described for the Push API e.g. in the WebRTC call notification use case. Do you envision this as a generic approach to supporting wakeup and message delivery for Webapps APIs? Using the example from the blog, I can imagine this looking like: 
	navigator.setMessageHandler("push", function(pushMessage) { ... });
	(and when starting up, call) navigator.hasPendingMessage("push");
Is that along the line of what you are considering?

Despite the name of the thread, "System Message" is the name of the API.

Received on Monday, 4 June 2012 17:05:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:09 UTC