Allow engines to sync independently of each other

RESOLVED WONTFIX

Status

P2
normal
RESOLVED WONTFIX
11 years ago
10 years ago

People

(Reporter: hello, Unassigned)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
Currently there is a single master 'sync' entry point in the Weave service that syncs all registered engines.  It should be made more flexible, so that it is possible to sync individual engines when necessary (for example, when we detect a change in a single engine's data).
(Reporter)

Updated

11 years ago
Depends on: 433915
(Reporter)

Updated

11 years ago
Target Milestone: -- → 0.2
(Reporter)

Updated

11 years ago
Priority: -- → P2
(Reporter)

Updated

11 years ago
No longer depends on: 433915
(Reporter)

Comment 1

11 years ago
We don't actually need this, the engine will decide which engines to sync and just sync those one after the other.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WONTFIX

Comment 2

11 years ago
Think about the possibility of using different sync strategy for different engines.
For example:
- sync cookies immediately on change
- sync bookmarks and passwords if age of last changes more than 30 sec
- sync history every 30 min
- check for any changes on server on start and every 30 min
(Reporter)

Comment 3

11 years ago
Yes, we plan to be able to get similar amount of control via bug 434816 and bug 433915.

Updated

10 years ago
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.