Collision management


davef1999

Recommended Posts

Are there any good workarounds for saving the "other" version in file change collisions?

My understanding of the current behavior is that when the same file on two machines is changed simultaneously, BTSync picks the newest and the "older" change is lost.

(a) Do I understand the behavior correctly?

(B) Is there some way to detect collisions and resolve them by hand?

My application is document sync, and every once in a while I end up w/changes on both sides of the sync. In those cases, I really really want to know & sort out the changes myself.

The late, lamented Windows Live Mesh, f.k.a Windows Live Sync, f.k.a. FolderShare would leave both files in the sync folder, tagged with the name of the machine. For example, if machine "Allice" is syncing with "Bob", and foo.txt is changed on both machines in between sync sessions (say, when both are on an airplane, disconnected from the 'net), then FolderShare would create "foo.txt.Alice" and "foo.txt.Bob" on both machines. Perfect.

Link to comment
Share on other sites

  • 1 year later...
  • 2 months later...
  • 2 years later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.