Services/Sync/WEP/109: Difference between revisions
Jump to navigation
Jump to search
Line 17: | Line 17: | ||
For our initial prototype, we will simply synchronize a list of Addons as a single WBO. The payload of the WBO will be an array of objects, each object storing the addon guid, version and clients on which it is installed. An example: | For our initial prototype, we will simply synchronize a list of Addons as a single WBO. The payload of the WBO will be an array of objects, each object storing the addon guid, version and clients on which it is installed. An example: | ||
[ | |||
[ | |||
{ | { | ||
"guid": "{340c2bbc-ce74-4362-90b5-7c26312808ef}", | "guid": "{340c2bbc-ce74-4362-90b5-7c26312808ef}", | ||
Line 34: | Line 33: | ||
] | ] | ||
} | } | ||
] | ] | ||
Revision as of 20:11, 7 September 2009
WEP 108 - Addon Sync
- Champions: Anant Narayanan <anant at mozilla dot com>
- Status: Draft
- Created: 07 Sep 2009
- Reference Implementation: None
- WEP Index
Introduction
Weave Sync should support synchronization of Addons. In this WEP, we describe a particular way in which this may be implemented.
Implementation
For our initial prototype, we will simply synchronize a list of Addons as a single WBO. The payload of the WBO will be an array of objects, each object storing the addon guid, version and clients on which it is installed. An example:
[ { "guid": "{340c2bbc-ce74-4362-90b5-7c26312808ef}", "version": "0.7pre2", "clients": [ "MyFennec", "MyFirefox" ] }, { "guid": "jetpack@labs.mozilla.com", "version": "0.5pre3", "clients": [ "MyFirefox" ] } ]