Closed Bug 726054 Opened 10 years ago Closed 10 years ago
Desktop parity: track last sync time from final upload, not final fetch
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.
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?
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.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee: nobody → rnewman
Target Milestone: --- → mozilla13
Product: Mozilla Services → Android Background Services
You need to log in before you can comment on or make changes to this bug.