Open Bug 584771 Opened 14 years ago Updated 2 years ago

Have applications initialize Sync at the appropriate time, rather than using implicit delayed initialization

Categories

(Firefox :: Sync, defect)

Product:
Firefox
Component:
Sync
Type:
defect

Tracking

()

People

(Reporter: philikon, Unassigned)

References

(Blocks 2 open bugs)

Details

Weave.js imports services.js 10 secs after final-ui-startup. It should leave it up to the application to do this.
As far as I can see, it now imports main.js: https://hg.mozilla.org/services/services-central/file/5fb27adf75a9/services/sync/Weave.js#l67 Still stuff to do here?
Well, I still think that Weave.js component is bogus. The app should be responsible for starting up Sync when *it* wants to (e.g. on idle?). Having Sync start up at some stupid random interval is just, well, stupid.
Summary: Get rid of service.js import in Weave.js → remove automagic Sync initialization, require apps to init on their schedule
Unintended consequences: on Fennec, where we start up ALL THE DAMN TIME, we end up not syncing the link you just opened… because Sync isn't running yet. Mammoth fail.
Priority: -- → P2
Summary: remove automagic Sync initialization, require apps to init on their schedule → fix init to be sane and app-appropriate
Looks like this might get fixed soon.
Blocks: 698955
Priority: P2 → --
Summary: fix init to be sane and app-appropriate → Have applications initialize Sync at the appropriate time, rather than using implicit delayed initialization
Blocks: 825728
Blocks: 823198
Thanks, Gavin. It does seem like a dep-aware execution queue would be a good solution to this… I'm going to mark that bug as a dependency, even if we end up doing the same thing differently.
Depends on: JSScheduleAPI
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.