On 30 Jan 2009, at 00:12, Antony Blakey wrote:
It's not a conflict, the edit document is simply refused by B. The
replication of the remaining documents will continue.
If a user on B also edits the document and it replicates to A, then
users of A will see a conflict, but users on B will not.
So replication doesn't necessarily result in consistent state
between nodes, with the further result that p2p meshes need to be
aware of this because homogeneity of the mesh would depend on
maintaining a consistent global order of updates, which isn't
possible.
Does this mean that this statement on the wiki overview: 'When
distributed edit conflicts occur, every database replica sees the
same winning revision' is no longer true?
Modulo validation & access control, the statement is still true.
Cheers
Jan
--
