This more about, how does the FTP server handle that.
While the server definitely is responsible for how it names files, and does (or doesn't) give them temporary/working names while they are actively being written to, I don't agree this is a server-only topic. A search on the Web will show this has long been a problem with FTP.
- I find it odd the server keeps writing while the client reads the same file
- I find it odd both the server-side AND client-side files are corrupt and unusable if I GET the files while they are actively being written to
- WinSCP has a REALLY nice looking, and robust Synch capability. What I'm suggesting is that it would be super-awesome if that feature set included accommodations for what seems to be a prolific and pervasive problem.
I coded a working solution that does not involve WinSCP using an algorithm/technique someone else suggested on the net, involving doing a DIR.. waiting.. doing another DIR.. DIFF-ing the two, creating a list of files that have not changed size/date/etc. GET that list of files only.
It works – active files are not downloaded.
Seems like something that could be part of WinSCP synch. A checkbox "[ ] Only Download IDLE server-side files"