- From: SULLIVAN, BRYAN L <bs3131@att.com>
- Date: Sat, 10 Mar 2012 00:43:28 +0000
- To: Ian Hickson <ian@hixie.ch>
- CC: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Yes, or more specifically (if this matters) invoke a Webapp, which at some level relates to a "page" as its root. This is different from the earlier discussion on extending SSE to connectionless event sources, as there's no assumption the Webapp is running in this case. If the Webapp *is* running, it's within the scope of what we have discussed earlier as SSE extensions (and not technically a "wakeup"). Thanks, Bryan Sullivan -----Original Message----- From: Ian Hickson [mailto:ian@hixie.ch] Sent: Friday, March 09, 2012 4:39 PM To: SULLIVAN, BRYAN L Cc: Stefan Hakansson LK; public-webapps@w3.org Subject: RE: Regarding app notification and wake up On Sat, 10 Mar 2012, SULLIVAN, BRYAN L wrote: > > 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. So basically you're saying you want to remotely cause a Web browser to load a Web page? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 10 March 2012 00:44:19 UTC