> On Apr 17, 2015, at 2:21 PM, Julio Albuquerque <[email protected]> > wrote: > > I am developing a routine to treat CONFLICTS, following tips from a > presentation by Jeff (I do not know if the name is correct).
Might be me :) > According to my need, I need to always save the newest possible revision, as > I do this? Since the structure of my documents I do not have a typeattribute: > Created in. > The revisions do not have date and time? Nope. Time isn’t very meaningful or useful in a fully distributed system. That’s for a number of reasons — you can’t guarantee that all devices have correct clocks; you can’t guarantee that devices report time truthfully; and if there are network partitions there can be a big delay between the time a revision is created and the time other devices see it. If you feel that timestamps are good enough for your use case, you can add them to documents yourself, and then use them to help resolve conflicts. > I noticed that conflicts are IEnumerable <SavedRevision> therefore always the > last line would be the youngest? I don’t have the .NET code handy, but I believe the ordering is by priority. The revision that’s been arbitrarily selected as the default (or “winner”) comes first. For most purposes you can consider the ordering of the rest of the revisions to be arbitrary/random. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/87D91683-99B7-457C-873B-1F6101DC1994%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
