Closed Bug 443739 Opened 16 years ago Closed 15 years ago

Sync on quit should be more selective on what to sync

Categories

(Cloud Services :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: hello, Unassigned)

Details

Sync on quit currently tries to aggressively sync all changes of all engines.  I think that makes it too expensive (time-wise) for the gain.

Instead, it could be sped up by limiting the engines it syncs.  For example, bookmarks and tabs are more important than cookies or passwords.

Another option is, instead of limiting by engine, to have an alternate score() method which returns how much the engine wants to sync _at quit time_.  Engines would essentially return their normal score, times some multiplier (e.g., 0.3 for cookies, and  3.0 for bookmarks).
I would say passwords and bookmarks are the most important things.  I do agree, of course this could also be caused by connection issues.  Sometimes I have trouble connecting to services.mozilla.com, and then I have trouble syncing when closing Firefox.
We aren't doing the sync on quit any longer.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
Component: Weave → General
Product: Mozilla Labs → Weave
Target Milestone: -- → ---
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.