Summary: This feature will enable to upgrade an installed application to the newer version. When updating, all application meta data and resource will be replaced by the application with a higher version number and the same application id, and all stored application data, like local storage, auto complete data etc., will be migrated to the newer application.
Spec: - https://docs.google.com/a/intel.com/document/d/1dhU1tMH10JDu2ADv1v5s7X65KW2Qf8iZDvoMPyP0aWQ/edit?pli=1#heading=h.b1116hcs7t39 - http://www.w3.org/TR/widgets-updates/ Affected component: xwalk/application Related feature in Jira: - https://crosswalk-project.org/jira/browse/XWALK-463 - https://crosswalk-project.org/jira/browse/XWALK-305 Target Release: Crosswalk-4/Crosswalk-5 Target Platform: Linux/Tizen Implementation details: I plan to enable the update feature by these steps: 1. Enable to update the application from local by providing a XPK package file path and update switch in command line, may look like this: ,---- | $ xwalk --update path/to/xpk_package.xpk `---- What we should do is adding a new method, ApplicationService::Update(), in which will check whether the new application version number is higher than the old one and the application id is the same between them, if yes, the update progress will be started, and all meta data and resources belong to the old application will be replaced by the new one, meanwhile, the application data, like local storage, will be migrated. 2. Implement the "update_url" field parsing handler in manifest. 3. Implement the update-info protocol (http://www.w3.org/TR/widgets-updates/#the-update-info-element) to support updating an application from remote server. 4. Enable to check application update status in Crosswalk runtime model if there is a valid "update_url" in application's manifest.json. -- Best Regards, He, Xinchao _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
