Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!ox.com!msen.com!emv From: emv@msen.com (Ed Vielmetti) Newsgroups: comp.archives.admin Subject: Re: archive normal form Message-ID: Date: 26 Jun 91 19:10:30 GMT References: <17493.Jun2607.22.3191@kramden.acf.nyu.edu> <20665.Jun2617.26.1691@kramden.acf.nyu.edu> Sender: usenet@ox.com (Usenet News Administrator) Organization: MSEN, Inc. Ann Arbor MI Lines: 29 In-Reply-To: brnstnd@kramden.acf.nyu.edu's message of 26 Jun 91 17:26:16 GMT In article <20665.Jun2617.26.1691@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes: 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... To give an idea of what the pathlogical cases are, here are some spots which I can't currently verify now (with my automated verification tools) because they require site-specific knowlege which my current scheme is missing. unt-library-list vaxb.acs.unt.edu:[.library] can't "dir [.library]"; must "cd [.library] ; dir" netlib research.att.com:/netlib/ different login and password to get to netlib gorebill nis.nsf.net:nsfnet:gorebill.1991-txt anonymous password must be guest; can't "get nsfnet:gorebill.1991-txt", must "cd nsfnet; get gorebill.1991-txt" oaklisp f.gp.cs.cmu.edu:/usr/bap/oak/ftpable/ can't "cd /usr; cd /bap"; must "cd /usr/bap/oak/ftpable". I agree that I'd like one token to specify the whole file reference if that's possible, if the syntax is rich enough to handle these cases but still human readable. I don't want to go to the ISO style tag=value business if it's avoidable. --Ed