Yes you are right TS
TS: indeed you are correct. I would like to use WinSCP as a replacement for rsync. Since I do rsync over ssh, I was assuming that it would be possible to also do this over SCP. Since WinSCP can establish an SSH connection to the server, why not simply have a remote shell command that can generate the CRC/MD5/SHA1/etc. checksums remotely, and then compare that to the locally-generated copy, during the "synchronize" process.
My problem with rsync is that it does not synchronize bidirectionally. Sometimes I have newer files locally, sometimes remote is newer. And the date alone is not always accurate (i.e., sometimes you just open Excel files and it changes the date even though nothing was changed). For this, the checksum method would save needlessly transferring the file and also changing the date.
There seems to be the capability of adding this to the "R" (versus "L" for local) command-set in my posting below, but perhaps I don't understand the integration of those commands and the synchronization process.
My problem with rsync is that it does not synchronize bidirectionally. Sometimes I have newer files locally, sometimes remote is newer. And the date alone is not always accurate (i.e., sometimes you just open Excel files and it changes the date even though nothing was changed). For this, the checksum method would save needlessly transferring the file and also changing the date.
There seems to be the capability of adding this to the "R" (versus "L" for local) command-set in my posting below, but perhaps I don't understand the integration of those commands and the synchronization process.