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

Re: Deliverables

From: Poussa, Sakari <sakari.poussa@intel.com>
Date: Mon, 4 Jun 2012 16:57:53 +0000
To: Jonas Sicking <jonas@sicking.cc>, Adam Barth <w3c@adambarth.com>
CC: "public-sysapps@w3.org" <public-sysapps@w3.org>
Message-ID: <CBF2369F.1780B%sakari.poussa@intel.com>
On 6/3/12 9:20 PM, "Jonas Sicking" <jonas@sicking.cc> wrote:

>The only API that I have an opinion on that we *should* include is
>what we at mozilla has referred to as "system messages API". This is
>an API which is used to deliver messages from the UA to a application,
>even when that application isn't currently running. I.e. the system
>messages API will deliver the message to the application, but if the
>application isn't running, the API first starts the application and
>then delivers the message.
>
>This is a capability we have found the need for in several APIs, such
>as the Alarm API, WebIntents/WebActivities and Push Notifications API.
>This is why I'd recommend that we include this in the initial set,
>possibly along with an API which would use this mechanism.

This is a good one. On Tizen we haven't done anything in this space other
than listed is as a gap. IMO, this is an important API to have, and we
should start working on it early on.

-sakari
Received on Monday, 4 June 2012 17:27:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 June 2012 17:27:47 GMT