Closed
Bug 726054
Opened 13 years ago
Closed 13 years ago
Desktop parity: track last sync time from final upload, not final fetch
Categories
(Firefox for Android Graveyard :: Android Sync, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla13
People
(Reporter: rnewman, Assigned: rnewman)
References
Details
(Whiteboard: [qa-])
Desktop Firefox downloads records, bumping the last sync time from a record high-watermark, and then -- if an upload occurs -- bumps to the response X-Weave-Timestamp.
This, of course, is a race condition: if anyone else uploads records between starting our fetch and finishing our upload, we won't see them.
But it does avoid the problem of uploading a record and downloading it again on the next sync. So let's do this until we have sessions.
Assignee | ||
Comment 1•13 years ago
|
||
Perhaps a compromise would be to track two lastSync times, and fetch from the earlier timestamp if info/collections reports a later time than our last upload?
Assignee | ||
Comment 2•13 years ago
|
||
The alternative is to cross-session track, perhaps by querying on ID before we fetch. All nasty. Sync isn't really designed for this whole "syncing" malarkey.
Assignee | ||
Comment 3•13 years ago
|
||
Comment 4•13 years ago
|
||
Assignee: nobody → rnewman
Target Milestone: --- → mozilla13
Updated•13 years ago
|
Whiteboard: [qa-]
Updated•12 years ago
|
Product: Mozilla Services → Android Background Services
Updated•7 years ago
|
Product: Android Background Services → Firefox for Android
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•