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).
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
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
Component: Weave → General
Product: Mozilla Labs → Weave
You need to log in before you can comment on or make changes to this bug.