Skip to content
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.

Clarify update aspects of lifecycle #80

Open
marcoscaceres opened this issue Apr 16, 2013 · 1 comment
Open

Clarify update aspects of lifecycle #80

marcoscaceres opened this issue Apr 16, 2013 · 1 comment

Comments

@marcoscaceres
Copy link
Contributor

Questions from mailing list:

Application update/uninstall behavior when it is running If an application is in running state, and at the moment RuntimeInstaller try to update/uninstall it, what should be the expected behavior?

And:

About application update, is it better to support auto-update through adding a ‘update_url’ in application manifest file?

@jmajnert
Copy link

jmajnert commented May 9, 2013

For the first issue, I think that if the ApplicationManagement.applyUpdate() is called on a running or paused app, then the app should be terminated and the update should be applied. I'm not sure if we should allow the application to execute its termination callbacks, but I'm leaning towards allowing it.

As for the second issue, auto-update is already possible by checking if the original manifest was changed? IMHO adding update_url to the manifest adds unnecessary complexity.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants