On Oct 29, 2:39 pm, "Simon B." <[EMAIL PROTECTED]> wrote:
> > Also, what happens next time I visit the app? Is it authorized to launch the
> >backgroundtask, or do I have to re-authorize it?
>
> Surely it has to stay authorized. Someone I asked even expected that
> authorization to follow them between different computers!
>
> > *Lifetime:* Do we need the "start onbrowserlaunch" option? What's the use
> > case for this?
>
> > *Process model:* Are there cases when abackgroundtaskwould need to
> > communicate with the tab that created it? For example, opening an event in
> > an existing calendar window.
>
> About Lifetime: users that pay for bandwidth, or have lack of RAM,
> might want to be able to close this process together with thebrowser.
> Those poor on RAM might also want the process to not start on Login,
> but only after thebrowseris started.
Good thought. We'll consider adding an option to the browser so that
the user can choose.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
