At the moment, the designed behavior locks further sync until the conflict
is resolved, consistent with the windows file copy/move model behavior.
Having said that, the scenario you mentioned is an interesting one, thanks
for pointing it out. As I mentioned before, this kind of feedback is very
important for us because we are constantly thinking of ways to improve the
Program Manager - Windows Live FolderShare
"Ndodge" <Ndodge@xxxxxx> wrote in message
> I am using foldershare to sync files between a work desktop and a home
> laptop. The work desktop is always connected, while the laptop is
> intermittently connected. I unknowingly left an application open with a
> open on my work desktop. At home, on my laptop, I moved the file to a
> different folder. When I got back to work, foldershare was understandably
> prompting me, telling me that it couldn't delete the file (because it was
> still open on my desktop). However, it appears that all of foldershare
> blocked, meaning none of the other many changes I had made to files on my
> laptop had been synced with my desktop. My laptop is shut off at home so
> can't get at the files today.
> Is this working as designed ?
> Or better, is this working as intentionally designed ?
> Isn't there a separate UI thread which deals with resolving issues via UI
> with particular files while another thread continues to operate in the
> background ?