Closed Bug 433914 Opened 18 years ago Closed 18 years ago

Allow engines to sync independently of each other

Categories

(Cloud Services :: General, defect, P2)

Product:
Cloud Services
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: hello, Unassigned)

References

Details

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).
Depends on: 433915
Target Milestone: -- → 0.2
Priority: -- → P2
No longer depends on: 433915
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
Closed: 18 years ago
Resolution: --- → WONTFIX
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
Yes, we plan to be able to get similar amount of control via bug 434816 and bug 433915.
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.