What's new:
* ftp can set modification time on remote files using either SITE UTIME or two
argument MDTM command (off by default).
* new settings ftp:use-site-utime, ftp:use-mdtm-overloaded.
Ftp now uses more Buffer objects, which can make it consume slightly more cpu.
That's the cost of utf8 recoding. Fortunately, I could not measure it precisely
even on transfer of 10M file.
Neither of SITE UTIME and two argument MDTM is enabled by default now.
I don't particularly like the overloaded MDTM, as it does not allow spaces
in file names. SITE UTIME is slightly better, ftp server can extract file name
with spaces by taking 4 arguments from the end of line, the rest in the middle
of line is the file name.
So I tend to enable SITE UTIME by default, but have not decided on it yet.
Does anybody know any better way to set file modification time over ftp
protocol?
Please test UTF8 support, or let me know of a server which supports UTF8 _and_
contains file names with non-ascii symbols.
lftp can be downloaded from the usual location:
ftp://lftp.yar.ru/lftp/devel/
http://ftp.yars.free.net/lftp/devel/
You can also use anonymous cvs access. See README.CVS in lftp/devel directory.
--
Alexander.
