On 28/05/2018 11:38 am, Ryan Kelly wrote:
However, once this first device has re-uploaded and restored a sensible-looking timestamp to the "tabs" collection, what will be the behaviour of other devices? It seems like this might prevent them from discovering that their own tab data has disappeared, and they'll only recover after user navigation triggers them to upload a new modified tab record.
Tabs are a little special - each client has exactly 1 record. Desktop further treats tabs as special by always uploading all tabs in the first sync for the session.
But yeah, in general you are correct - other desktop devices already running may not recover until the browser is restarted.
Thom has an interesting suggestion in the meeting last week, that we could force clients into doing a full re-sync of a collection by modifing the "syncid" for that collection in their meta/global record. Would this be a more reliable (albeit more hacky!) way to guide the clients into correct behaviour here?
Yes, that should force clients to re-upload all of their tabs on the very next sync. Note also that simply removing tabs from meta/global should have the same result (the fist client to Sync should generate a new syncID)
Mark _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
