🚀 go-pugleaf

In article <WORLEY.91Jun26104902@sn1987a.compass.com> worley@compass.com (Dale Worley) writes:
> However, FTP is oriented to "directory and file name" access -- you CD
> to a directory, then you GET a file.  Thus, it's best to have two
> fields -- the first one is "the argument to give to CD" and the second
> is "the argument to give to GET".

Sorry I didn't make myself clear. The real ftp model is that you do zero
or more cd's, then a get. That's what ftp supports, after all...

Why doesn't the single-directory, single-filename model work? Because
there are some operating systems where you *have* to do cd foo, then cd
bar, then get blah. You *cannot* do a combined cd and then get blah, as
you can under UNIX. Furthermore, there are many operating systems which
have no way to state ``current directory''. You *cannot* do a ``null
cd'' and then get blah, as you can under UNIX.

So it's best to have any number of fields, each meaning ``give this
field to cd'', and then a final field meaning ``get this.'' A name like
pub/foo/bar reflects this perfectly: cd pub, cd foo, get bar. Similarly,
a simple name like readme.txt means don't do any cd's, just get bar.

---Dan