Jeff Amiel <jamiel at istreamimaging.com> writes:
> To that point, think about the complexities in dealing with merge conflicts.
> Client A (offline) makes a change to record 12345
> Client B (offline) makes a change to record 12345
>
> Merge takes place.
> Who's change becomes effective?
> Last man in the pool?  How do you let Client A know that his changes 
> never became effective.?

Yes, that's the "standard" problem with multimaster replication.

With a PalmPilot, what happens is that the offending records get
duplicated, and you get a note in the "sync log" telling you to fix
the conflict.

I don't recall what Lotus Notes did in such cases; possibly similar.

It is not evident that "huge, expensive multimaster replication
systems" do anything that is substantially more sophisticated than
this...
-- 
output = ("cbbrowne" "@" "ca.afilias.info")
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)