Just to record some details on this: we've seen (in fact, I've seen personally!) data loss in Sync 1.1 from last write approaches, so some caution needs to be used here. There are two definitions:
* You look at timestamps. Clock drift is a real issue in the wild. * You use "last server write wins". The former is obviously flawed. The latter is very vulnerable to service unavailability, particularly in the current Sync infra where server data can disappear. I go into a little more detail on that in one of our requirements docs: https://services.etherpad.mozilla.org/2019 -R ----- Original Message ----- From: "Andreas Gal" <[email protected]> To: "Lloyd Hilaiel" <[email protected]> Cc: [email protected] Sent: Friday, July 26, 2013 12:09:41 PM Subject: Re: whats the key anyway? I have no opinion on conflict resolution. Many good approaches are valid. I don't care about which one we use per type. Last write is fine IMO for everything. Which key approach we use is critical, however. Otherwise finding the dupes will be difficult in the client. Andreas Sent from Mobile. On Jul 26, 2013, at 12:06, Lloyd Hilaiel < [email protected] > wrote: On Jul 26, 2013, at 1:03 PM, Andreas Gal < [email protected] > wrote: In short, what I heard yesterday ("lets copy data in case of conflict") is a noble theory, but I am afraid wrong in practice, and I would like to hear comments on the observation above. Sounds like you're refining that theory. That conflict resolution is type specific. For passwords - most recent change wins. For bookmarks, tabs and history - favor duplication over deletion. ? lloyd _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
