On 08/09/2012 04:06 PM, Anant Narayanan wrote:

> Jonas identifies the following problems with the mechanism we have in
> place now:
> 
> a) The onus is on the developer to ensure that updates to the OWA
> manifest and AppCache manifest are in lock-step.
> 
> b) If a developer wants to change something like launch_path, the old
> launch_path must be kept around for an indefinite period since it is not
> possible to know when all clients have upgraded.
> 
> In order to mitigate (a), we can have the AppCache update code also
> update the OWA manifest whenever a change in the AppCache manifest is
> detected. There is no easy answer to (b), since it pretty much
> impossible to ensure manifests at all clients have been updated, so any
> solution will always break (hopefully a very small number of) clients.
> 
> I've filed https://www.bugzilla.mozilla.org/show_bug.cgi?id=781685 to
> have AppCache perform an app upgrade if necessary. I also propose we add
> the following pieces of functionality to better manage updates:

I'm not convinced that the complexity of doing that at the offline-cache
level is worthwhile since we will check for updates to the apps manifest
and the appcache manifest for apps that declare it at the same
frequency. So the risk of getting out-of-sync is fairly low imho.

> - Keep polling for manifest changes in Firefox, WebRT and/or a
> background process, once a day. A HEAD request to the manifest URL
> should suffice.
> 
> - If a change was found, a silent update can be performed if there were
> no changes to the name of icon. If the name or icon is changed, the user
> must be prompted (easy to do if the app is currently running, if not
> prompt at the next time the app is launched).

I think we must provide UI hooks without any criteria, and let the UI
decides when to prompt the user. This will let UX people be creative ;)

        Fabrice
-- 
Fabrice Desré
b2g Team
Mozilla Corporation
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps

Reply via email to