app-lifecycle spec

Hi all,

I'm really sorry for asking this question at the first place. Just wondering if there's anybody here has seen this :

https://developers.google.com/chrome/apps/docs/background

It looks to me that what they have there is pretty much answering all the requirements mentioned in the app-lifecycle spec section 4.7.

I personally think that their approach in hooking / configuring it up at the manifest level is better rather than bringing in the concept of main() into web-apps like proposed in the app-lifecycle spec.

Is there any reason why we don't want to just adopt the similar approach and extend it as per-necessary instead ?




Another point regarding the section 4.5 of the app-lifecycle spec, it's mentioned :

"A typical browser-driven use case for system events is an email application that wants to show a desktop notification when a push notification is received so the user is informed that there are new emails even though the tab in which the email application was running has been closed."

In this specific use case, would it be rather the email application that should have a background task running and responsible to keep checking for new email in the server, and when it does, the email application is the one that will send request to the system to display desktop notification ?


Thanks,
Darmawan.






________________________________
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus