Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!HOGG.CC.UOREGON.EDU!jqj From: jqj@HOGG.CC.UOREGON.EDU Newsgroups: comp.protocols.tcp-ip Subject: Re: syntax of remote pathnames? Message-ID: <8903281410.AA04667@hogg.cc.uoregon.edu> Date: 28 Mar 89 14:10:43 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 14 If you are serious about coming up with a generic standard for remote file names (something that could be an RFC, say), then you have to recognize the fact that file names (aka path names) can be pretty arbitrary. FTP constrains them not to contain CRLF (I think...), but one could even imagine a file system that allowed CR, LF, or CRLF in a pathname. More importantly, pathnames often depend on login information. In addition to Unix-style relative pathnames, remember that many implementations do the equivalent of a Unix chroot() when you log in as ANONYMOUS, so the directory tree is substantially different from what a use logging in with some other user ID would see. A widely used and fairly robust syntax for specifying remote file names is: ""::CRLF