canmove, Confirmed users
1,570
edits
Firefox/Go Faster/Client Implementation Plan: Difference between revisions
Jump to navigation
Jump to search
Firefox/Go Faster/Client Implementation Plan (view source)
Revision as of 22:38, 22 July 2015
, 22 July 2015Link to the update manifest docs
(Initial implementation plan) |
(Link to the update manifest docs) |
||
| Line 22: | Line 22: | ||
* '''Bug: Test that automated updates for the system add-ons location function correctly''' | * '''Bug: Test that automated updates for the system add-ons location function correctly''' | ||
During runtime the client will periodically check for system add-ons to use with the current application version. It will do so by making a HTTPS request to a specific URL which will return a root manifest listing the system add-ons for that application, the versions they are compatible with and the URL of | During runtime the client will periodically check for system add-ons to use with the current application version. It will do so by making a HTTPS request to a specific URL which will return a root manifest listing the system add-ons for that application, the versions they are compatible with and the URL of a normal [https://developer.mozilla.org/en-US/docs/Extension_Versioning,_Update_and_Compatibility update manifest] for each add-on. | ||
* '''Bug: Periodically download the system add-ons root manifest''' | * '''Bug: Periodically download the system add-ons root manifest''' | ||
| Line 46: | Line 46: | ||
} | } | ||
There is some duplication of information here. The min/maxVersions are also present in the update | There is some duplication of information here. The min/maxVersions are also present in the update manifest but including them in this root manifest allows us to decide what new add-ons need to be installed and which need to be removed without making any secondary requests. | ||
The actual host of the update manifest and the XPIs that it points to doesn't matter to the client code. It could be AMO or something new. | The actual host of the update manifest and the XPIs that it points to doesn't matter to the client code. It could be AMO or something new. | ||