Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
What is the expected behaviour in the following scenario RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Say i have two machines 'A' and 'B' which has a synced folder of some DLL files 

    now the dlls on machine A are updated 

    and the MESH starts synchronizing the folder to machine 'B'.

    after some random time (before the sync process completes), 

    the machine 'A' gets disconnected from the internet.

    Lets assume that 40 %  sync was done .( say there are 40 dlls and 18 of them were synced )

    In this scenario, since the source for the sync is not available,

    are the synced dlls reverted back to the previous version??

    Microsft Student partner,ISSC, university of Pune
    Friday, November 21, 2008 2:29 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Live Mesh does not currently have any file versioning feature - though this is a popular request (and please feel free to add your vote for this to our Suggestions sticky).  Given your description of the scenario you're interested in, however, I don't think that Live Mesh will currently meet your needs.  The primary issue, it seems to me, is that Live Mesh attempts to keep your files up to date - if some files are updated, and then the remote machine goes offline, Live Mesh does not see that as a "sync failure": it successfully synced some of the files, and will simply wait to sync the others.  If you need either all or none of the files to be up-to-date (which is what I believe you're saying - though please correct me if I've misunderstood), Live Mesh does not currently have a way for you to make sure that's the case.  Again, though, please add any suggestions for functionality you'd like to see in the future to our Suggestions thread.

    Thanks,

    Ben.
    Monday, November 24, 2008 5:57 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi,

    Once the files are updated they should remain that way.  The files that were not updated won't be if there is no source for them to update from, but the files that were updated will not revert after being synced.

    I hope that is what you were looking to know.

    Ben.
    Friday, November 21, 2008 8:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Well, Lemme Tell you the exact scenario where i wish to use Live Mesh.

    I have a dev server in India. Here The Dev team publishes a web app and some web services on the dev server.

    Now whenever there is a deployment on the server here in india, I wish to sync it to some server in the US say. so that once a build of the software is pushed to the Indian Server, The US server too has it.

    Now say when the two folders are syncing, there is a connection loss on the either end. In that case, 
    Is there a  way by which i can revert back to my old Version of the web app on the destination if i detect that the sync failed
    Monday, November 24, 2008 3:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Live Mesh does not currently have any file versioning feature - though this is a popular request (and please feel free to add your vote for this to our Suggestions sticky).  Given your description of the scenario you're interested in, however, I don't think that Live Mesh will currently meet your needs.  The primary issue, it seems to me, is that Live Mesh attempts to keep your files up to date - if some files are updated, and then the remote machine goes offline, Live Mesh does not see that as a "sync failure": it successfully synced some of the files, and will simply wait to sync the others.  If you need either all or none of the files to be up-to-date (which is what I believe you're saying - though please correct me if I've misunderstood), Live Mesh does not currently have a way for you to make sure that's the case.  Again, though, please add any suggestions for functionality you'd like to see in the future to our Suggestions thread.

    Thanks,

    Ben.
    Monday, November 24, 2008 5:57 PM