[Unison-hackers] Other synching configurations

[Alan Schmitt]

On 18 nov. 05, at 16:05, Jerry Haltom wrote:

> So why does Unison only work well in a hub layout?

Consider the following scenario: you have three replicas, A, B, C  
with one file containing "init", and each one synchronizes with the  
others. A modifies the file to "foo" and syncs with B. Then B syncs  
with C. So all replica are in the same state and synchronized. Now  
imagine C changes the content of the file to "bar" and synchronizes  
with A. Intuitively, the change should propagate, but instead a  
conflict is detected, because from the point of view of unison, A and  
C previously had "init" and now one has "foo" and the other "bar".  
What is missing in this case is a way to propagate the  
synchronization state between synchronization pairs.

I hope this makes things clearer.

Alan

-- 
The hacker: someone who figured things out and made something cool  
happen.
.O.
..O
OOO




-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.seas.upenn.edu/pipermail/unison-hackers/attachments/20051120/69717801/PGP.pgp