I'm using this over FTP.
Please try to describe in more details what do you mean by "all the local changes are done".I'm finding that many files are being missed that are only picked up with a full synchronize after all the local changes are done.
It should not be problem generally. May depends on your answer above.Is it possible that so many local changes are happening that winscp can't keep up?
There's a delay of 500ms currently. It can be changed in registry (or INI file) only.If this is a problem, would it help to have a "delay" option so that winscp would keep track of what changes have been made, but only start transferring after a specified delay, to allow local changes to have settled down?
Yes the former is true. However I believe that Windows should trigger another change notification if A/B changes after C. So WinSCP should perform two synchronizations in row.How does the keepuptodate function work? Does it notice a change in a folder, and synchronise ALL files in that folder (transferring only changed files of course, after comparing local with remote), or does it know exactly which files have changed, and synchronise only those? If it is the former, say a big file C changes, and this starts winscp off transferring C, then WHILE C is tranferring, files A and B in the SAME folder change, is there a danger that A or B is overlooked because they are before C in some order within the folder (alphabetical and/or time)?
You can post new topics in this forum