canmove, Confirmed users
409
edits
Services/Sync/Features/Addon Sync: Difference between revisions
Jump to navigation
Jump to search
Services/Sync/Features/Addon Sync (view source)
Revision as of 19:33, 29 November 2011
, 29 November 2011add operations notes
No edit summary |
(add operations notes) |
||
| Line 135: | Line 135: | ||
This is the first component of Sync which will indirectly communicate with a non-Sync server (addons.mozilla.org). Sync will be talking with it via the AddonRepository JS APIs. Sync assumes those APIs are doing the proper things to secure against MITM attacks, etc. | This is the first component of Sync which will indirectly communicate with a non-Sync server (addons.mozilla.org). Sync will be talking with it via the AddonRepository JS APIs. Sync assumes those APIs are doing the proper things to secure against MITM attacks, etc. | ||
|Feature operations review=This feature will utilize a new server-side collection, *addons*. The server people might want to add it to the known/common collections set. | |||
When add-ons are synced across devices, the receiving device installs the add-on from addons.mozilla.org, not from Sync. For every add-on to be installed on receiving devices, AMO will see traffic. It will first see a search for this add-on by its ID. If that returns something, the XPI will be downloaded as part of the install process. | |||
When this feature launches and add-ons are synchronized across devices, AMO could see increased activity. We should keep an eye on this for launch day. | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||