Mark Finkle wrote:
I think we should be very careful to solve the problem we are
trying to solve here, not a more general problem we don't care
about. As a user, I won't be editing my bookmarks concurrently on
two devices with any significant frequency. Even in those cases
having a guaranteed consistent hierarchy wins in my opinion.
One-doc-per-bookmark has a nightmare to keep consistent in the
presence of mutation, let alone concurrent mutation overlayed with
a replication mechanism.
I agree with the "I won't be editing my bookmarks concurrently on two
devices", but I wonder if "we're a family using the same Firefox
desktop profile (hence the same Sync account) but using different
devices tied to that account" is typical enough to cause us to keep it
in mind when thinking about concurrent operations.
*Something* is causing the non-trivial amount of corruption/races in
our current Sync system. Maybe it's not the example I present, but if
it exists in the current system, I don't think we should quickly
simplify it away.
Current sync doesn't trigger a sync on change on the other linked
devices. That can definitely significantly prolong the conflict window.
Andreas
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
