Provide service for extensions to register extension data to be synced

RESOLVED FIXED in Future

Status

Cloud Services
Firefox Sync: Backend
P4
enhancement
RESOLVED FIXED
10 years ago
7 years ago

People

(Reporter: Jaime Mitchell (use bugmail@jaimem.org.uk for email), Unassigned)

Tracking

unspecified
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa-])

Weave should provide a way for an extension to register its data (possibly only in the users profile directory) which would be then be stored in the cloud for use on multiple machines

For example
Adblock filter lists
Grease Monkey Scripts
Stylish user styles

Weave should probably provide an user interface in the settings to select which extensions data is uploaded

Comment 1

10 years ago
Leaving this one for a future version (potentially).
Priority: -- → P4

Updated

10 years ago
Target Milestone: -- → 0.3
This would be very useful for my Session Manager extension as I've had people request the ability to sync sessions between browsers.

Comment 3

10 years ago
This would be very valuable to extension developers and seems as if it would also help establish Weave as the standard for synchronization of browser profile data. Users would be able to use a single interface to manager all their data synchronization rather than having to learn a separate approach for each extension which provides that feature.

Some specifics on what would be nice to see in this:

- the ability for extensions to register additional data types for sync, and include in their installation packages derivations of Weave's Engine class to tell it how to sync their data (and to overlay Weave preferences with appropriate elements for configuring their data synchronization). Weave does already support data-type specific synchronization engines but I think it would also need to support derivations of the SyncCore class per data type to provide per-data-type conflict resolution strategies.

- enabling the user to specify an alternate server url per data type (or more generally, per extension, applicable to all data types registered for that extension)

- the ability to extend the sharing functionality to have more fine-grained control over how shared data is used (i.e. rather than just syncing the data as-is, allowing the extension to access shared data directly on the server applying its own business logic to determine how to make use of it)

Comment 4

9 years ago
These bugs need to be triaged, removing 0.3 milestone setting.
Target Milestone: 0.3 → Future

Updated

9 years ago
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general

Updated

9 years ago
Component: General → Sync
QA Contact: general → sync

Updated

8 years ago
Blocks: 530399

Comment 5

8 years ago
The way I see it, you're almost there with Collections, and the ability to publish addons from a given computer to collections directly.

What would be really cool is an extension that would automatically install extensions in a Collection to systems have registered with Weave.

Comment 6

8 years ago
I'd like to see AddOns synced, but not inline with regular data. Perhaps a weekly or on-demand job. I'd be happy to pay a small annual fee if it meant my /entire/ Firefox browser was kept in sync, as it would save me from having to use MozBackup on a regular basis.

Comment 7

8 years ago
That would be nice to all sorts of useful addons. Like PasswordMaker.
Don't have to save on a USB flash drive OR a FTP server.
how is this bug doing? has it been replaced by another or what is the current work status on this?
This capability already exists, actually.  We'll be making sure docs are published by the end of the year to explain best practices around how to write a Sync engine.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED

Updated

7 years ago
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.