Ftp-WG: mdtm and mlsd commands

I believe that the probability of that happening would be next to nil,
although not impossible. I can see how certain errors may arise in the
path/file portion of the sequence, for example: "MDTM 20040502185322
file.FILE/member.MBR", on an OS/400. However most non-NT/*nix systems don't
support MDTM-query, let along MDTM-modify in the first place. Also, when our
client issues MDTM-modify sequence, it rarely (ever?) uses the absolute
path, so "MDTM YYYYMMDDHHMMSS <FILE_NAME>" (relative to current dir) is the
most likely scenario...and no "fatal" errors reported by our users yet
(knock on wood).

Anyway, popular clients like ws and cute should probably support the newest
standards, such as the proposed MFxx by David Somers, even while
grandfathering the popular (albeit informal) mdtm-modify sequence currently
supported by many clients and servers.

Robert Oslin


-----Original Message-----
From: ftp-wg-owner [mailto:[email protected]]On Behalf Of Mark
Symons
Sent: Wednesday, February 04, 2004 5:24 PM
To: FTPEXT Working Group
Subject: Ftp-WG: mdtm and mlsd commands


> The MTDM modify command syntax used is:

> MDTM YYYYMMDDHHMMSS [<REMOTE_PATH>]<FILE_NAME>

> Works for file names with and without spaces and/or paths.

> Please educate me on why this would be fatal.

Because "YYYYMMDDHHMMSS [<REMOTE_PATH>]<FILE_NAME>" (the whole string) can
itself be a legitimate filename?

Mark Symons
Ipswitch, Inc
Augusta GA