[Unison-hackers] Other synching configurations

[Dale R. Worley]

On Sun, 2005-11-20 at 10:29 +0100, Alan Schmitt wrote:
> 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.

This scenario could be cured by having C sync with A before the file is
changed to "bar".  Perhaps a rule of thumb is that if one makes a cycle
of sync relationships, one has to keep all of the relationships updated,
not just the replicas they connect.

Dale