AMO:Users/Software Updates: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{amo}} | |||
=Overview= | =Overview= | ||
This page describes the method that Toolkit applications will handle addons and their updates. For the purposes of examples, Firefox will be used. Addons currently supported are themes and extensions. | This page describes the method that Toolkit applications will handle addons and their updates. For the purposes of examples, Firefox will be used. Addons currently supported are themes and extensions. | ||
| Line 15: | Line 17: | ||
=Links= | =Links= | ||
* [[Software Update|Application Updates]] | * [[Software Update|Application Updates]] | ||
* [[Update:Checking_For_Updates|Checking for Updates] | * [[Update:Users/Checking_For_Updates|Checking for Updates]] | ||
Revision as of 06:18, 29 April 2007
Overview
This page describes the method that Toolkit applications will handle addons and their updates. For the purposes of examples, Firefox will be used. Addons currently supported are themes and extensions.
Requirements
- Support for silent or explicit downloading
- Support for cryptographic signatures
- Minimize impact on backend build and distribution processes
- Allow users to easily view and control the process
Downloading the Update
Firefox will periodically check the Mozilla.org update servers (addons.mozilla.org aka AMO) for available updates. The update server will return a manifest file (which is a simple XML file) over HTTPS that will point Firefox at the right update package to download. A separate check is made for each addon.