>> OK, it's been some years since I have had the time to
stay up to
>> date with these things. How does it handle relative remote paths?
>> Is there a special syntax for filenames in my remote home
>> directory? Without this, editing remote files would still be a
>> pain.
> Unfortuantely, no, but the answer is fairly obvious:
> ftp://user:passwordļ¼ host/~/filename (should hit the location where
> ftp starts, which will be your home directory).
Again, see RFC-1738. I don't know what Netscape needs, but the "~/"
in the above example is redundant (or might not even work) against
some servers. Do all servers support "CWD ~"?
What you get is more close to what you'd expect. You know, as if the
people who wrote RFC-1738 were also FTP users. You log onto the
remote system using the user name and password. The first "/" is just
a delimiter telling you where the hostname stops. Things after that
are what you'd feed to FTP CWD (or "cd" in most ftp client
implementations). If you need to use a literal slash, it has to be
encoded using the usual URL encoding rules.
So, the answer to your original question is that there isn't a special
syntax for things relative to your remote home directory. That's the
more or less default view. You could consider it to be a special
syntax to access absolute pathnames (you put a "%2f" where you'd
expect the root "/" to be).
--
bill(a)carpenter.ORG (WJCarpenter) PGP
bill(a)bubblegum.net 0x91865119
38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3