MDTM - reversability Filedate copy-direction?

[Atreyu]

I just downloaded WinCMD 6 an checked out some of it's new features...

I wanted to try the MDTM feature of the synchronize directories. When syncing files via ftp, it sets the local filedate to the servers' system time, while I expected it to keep the local filedate and set the file on the server to the same time.
This is not reversable I think..

Is this a server-setting which WinCMD has to comply to or is it a choice of WinCMD?

If it's a server-setting, I can understand as the server-owner might want to have control over the filedates.
If not I wonder why it's implemented like this, as the date the file is modified seems more important to me than the date a file is uploaded.

Any opinions? Am I overlooking something?

[havanna]

This is standard filesystem behaviour, whenever you write a file to FTP it will get current date and time. There is no way known to me to avoid that.

TC's behaviour of changin Timestamp in local files is very useful when you want to sync a large tree to ftp.
I think this makes sense, usually I want to sync my server immediately after having edited some files.

[ghisler(Author)]

MDTM is only sent to the server if the server reports to support it in the FEAT command!

[Atreyu]

I just wondered what exactly the feature of MDTM meant, but as I understand it now, it allows the setting of a filedate on the server, IF the server supports it.

Unfortunately IIS doesn't seem to do this. Also, the IIS-server has some time issues. I guess we'll have to resolve them first.

Thanks for your replies anyway.

[ghisler(Author)]

Indeed setting the time with MDTM isn't defined in any RFC (Internet standards document), only in some suggestions (drafts). The defined MDTM command only allows to RETRIEVE the file date/time. Therefore only a few FTP servers support MDTM this way, and that's why I'm adding it only now.