Re: [Task Scheduler] scheduling flexibility

Those just seem like async events to me, just like "app launched", "lost
network connection" etc. Chrome Apps have events like these which will also
wake up the app if not running.

Kenneth


> Should developers also be able to schedule background tasks for non
> time-based triggers e.g. allow task scheduling for the next time their
> device is 'idling' or 'plugged-in' or 'online' also? i.e. run my
> background task when the device next has a connection to the Internet
> otherwise _indefinitely_ delay its execution until that condition is
> met.
>
> It may also be good for user agents to be able to throw UA-defined or
> developer-defined timeouts and other errors against a given scheduled
> task and for web-apps to be able catch such scheduled task error and
> timeout events. These events would need to be delivered back to the
> web app at a time chosen by the UA along the same lines as the
> heuristics identified above. Or perhaps timeout and error events
> should occur silently (which removes the need to wake up the web app
> just to inform it it failed. Kind of cruel, perhaps).
>
> br/ Rich

Received on Tuesday, 5 November 2013 18:14:43 UTC