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:51, 23 July 2015
, 23 July 2015A little more info on the app path hash
(Improve notes about AMO's signing service) |
(A little more info on the app path hash) |
||
| Line 8: | Line 8: | ||
The specific path to the install location will be '''<profile>/features/<app path hash>'''. "app path hash" is a simple hash of the client's install directory. This means that if a user is using two different versions of the client application (say a developer version and a release version) with the same profile they will use two different directories for the system add-ons allowing them to be updated independently. When a single build updates to a new version it automatically retains the most recently downloaded system add-ons from the previous version. The majority of users use a single build and so will have just one directory in use. | The specific path to the install location will be '''<profile>/features/<app path hash>'''. "app path hash" is a simple hash of the client's install directory. This means that if a user is using two different versions of the client application (say a developer version and a release version) with the same profile they will use two different directories for the system add-ons allowing them to be updated independently. When a single build updates to a new version it automatically retains the most recently downloaded system add-ons from the previous version. The majority of users use a single build and so will have just one directory in use. | ||
The hash can be short to avoid causing path length problems and quick to generate. Collisions aren't a big problem, the client will recover gracefully automatically. | |||
* '''Bug: Create a features install location with a lower priority to the profile location''' | * '''Bug: Create a features install location with a lower priority to the profile location''' | ||