Two Spirit <[email protected]> writes: > If the algorithm is "last writer wins", then any edits by the other > disconnected half are lost. Wouldn't it make sense to approach it like a > source control merge conflict where both revisions are preserved and > presented to the user for the user to resolve? Depending on the length of > outage, this could be significant data loss. Even for short outages, if the > two halves are unaware of the disconnect, you've got unknown data loss. I > think unknown data loss is even worse than known data loss, because you > don't even know to go try to retrieve backups. I don't think it is right > that data just vanishes without some kind of red flag or ERROR message. Is > there any sort of journaling going on to get a list of the exact changes > somewhere?
Coda does this; see the code and papers at www.coda.cs.cmu.edu
pgpEptmeB7wpq.pgp
Description: PGP signature
_______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
