Terje Bless wrote:
On 22.06.01 at 08:48, Stephen J. Turnbull <turnbull(a)sk.tsukuba.ac.jp>
wrote:
>The "right" solution to this kind of problem (short of AI) is to make
>the program speak the language that EFS expects.
Well, I'd argue that the "right" solution is to speak FTP directly using
either internal protocol support or some library. I've seen the "we'll just
fake user input to an interactive FTP client" fail. Repeatedly.
Spectacularly. This is one example; the kerberized ftp in Red Hat another.
yes. i very much agree.
OTOH, doing FTP protocol support in Lisp may be a /leeetle/ overkill as
concerns this particular problem. :-)
i don't think it's overkill. is the ftp protocol really that hard? it's
hard
to believe this. all or most other programs do implement ftp directly.
probably the code to parse the ftp.exe output is just as hairy. 99% of the
windows efs problems would magically disappear if we implemented the protocol
directly.
--
ben
I'm sometimes slow in getting around to reading my mail, so if you
want to reach me faster, call 520-661-6661.
See
http://www.666.com/ben/chronic-pain/ for the hell I've been
through.