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

Re: Deliverables

From: Erik Kay <erikkay@google.com>
Date: Mon, 4 Jun 2012 10:48:58 -0700
Message-ID: <CA+bn54AsZ_Y6R2+HbGzAe4t9mc-7RdLk3W7Z6eKHi5HL_PROqA@mail.gmail.com>
To: "Poussa, Sakari" <sakari.poussa@intel.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Adam Barth <w3c@adambarth.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>
On Mon, Jun 4, 2012 at 9:57 AM, Poussa, Sakari <sakari.poussa@intel.com>wrote:

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

I also agree that this is important functionality to define.  I'm not
necessarily sure that it will need to be its own separate API
specification, or whether it will be part of the execution model.  From my
standpoint it will tie in pretty deeply into application startup, lifetime,
etc.

Erik
Received on Monday, 4 June 2012 17:49:28 GMT

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