Opened 19 years ago
Last modified 19 years ago
#2324 closed Feature request
MDTM implementation
| Reported by: | lesd | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Server |
| Keywords: | Cc: | lesd, Tim Kosse | |
| Component version: | Operating system type: | ||
| Operating system version: |
Description
Quote from codesquid from an earlier bug report
MDTM cannot be used to set file timestamps.
Example: MDTM 20050726131800 foobar
What does this command do? Set timestamp for the file
'foobar' or get timestamp for the file '20050726131800
foobar'?
Due to this conflict, MDTM should only be used to get
timestamps.
This is a feature that I badly need and have been
assured that many other FTP Servers do implement it.
Surely the ambiguity is only there if a file of that
name *does* exist. If not then can FZ not accept the
command as a request to update the timestamp?
In addition, the likelyhood of having such a filename
must be so remote that the default should be to update
file 'foobar' with what is a valid timestamp and only
if the file does not exist should FZ try to find a file
with name '20050726131800 foobar' and return its
timesatamp.
Please could you re-consider, as this feature would
make the life of synchronization programs so much
simpler and more reliable.
Thanks.
Sorry, but I don't plan to implement an unspecified and
potentially unsafe command extension. Please feel free to
design and formally specify a correct extension to the ftp
protocol.