canmove, Confirmed users
1,570
edits
Firefox/Go Faster/Client Implementation Plan: Difference between revisions
Firefox/Go Faster/Client Implementation Plan (view source)
Revision as of 17:52, 23 July 2015
, 23 July 2015Reordering
(A little more info on the app path hash) |
(Reordering) |
||
| Line 47: | Line 47: | ||
} | } | ||
} | } | ||
Here a specific maxVersion is present but we could equally use a maxVersion of "*" (or say that a missing maxVersion property defaults to "*") to say that a system add-on is compatible with all future versions and then change that at a later date. | Here a specific maxVersion is present but we could equally use a maxVersion of "*" (or say that a missing maxVersion property defaults to "*") to say that a system add-on is compatible with all future versions and then change that at a later date. | ||
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. | ||
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. | |||
=Securing system add-ons= | =Securing system add-ons= | ||