“last” is an interesting in distributed systems, a common approach is “the last item that arrived at the server”, as that can be guaranteed reasonably. It’s worth clarifying that.
On Jul 26, 2013, at 21:09 , Andreas Gal <[email protected]> wrote: > 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
