Ian, Stefan may respond with more detail, but the use cases we submitted for WebRTC consideration describe this as the ability to invoke an application and pass an event to it, whether it is running (or not) at the time of the event reception by the device. By running I mean that the app, or its user agent (in the case of a web app executing under a user agent), are not currently executing on the device, in any state. This "wake up and deliver" capability may require a multi-step device-internal process, but the overall goal covers both actions.
Thanks, Bryan Sullivan -----Original Message----- From: Ian Hickson [mailto:i...@hixie.ch] Sent: Friday, March 09, 2012 4:09 PM To: Stefan Hakansson LK Cc: public-webapps@w3.org Subject: Re: Regarding app notification and wake up On Fri, 9 Mar 2012, Stefan Hakansson LK wrote: > > The webrtc WG has identified that the ability to notify, and possibly > wake up, a web application of incoming events is important. This to > enable support of use cases such as incoming calls. And in certain > scenarios the resource use (e.g. power) is very important. What exactly do you mean by "wake up"? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
