# Re: FTP syntax

Dirk Herr-Hoyman (hoymand@joe.uwex.edu)
Tue, 8 Mar 94 08:52:49 -0600

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Fabio Metitieri: "Info Req."
- Previous message: Alan Emtage: "Re: FTP syntax"
- Maybe in reply to: Mitra: "FTP syntax"
- Next in thread: yandros@MIT.EDU: "Re: FTP syntax"
- Reply: yandros@MIT.EDU: "Re: FTP syntax"

    Date: Tue, 8 Mar 94 08:52:49 -0600

    Message-Id: <9403081452.AA26711@joe.uwex.edu>

    To: bajan@bunyip.com (Alan Emtage), mitra@pandora.sf.ca.us (Mitra),

    From: hoymand@joe.uwex.edu (Dirk Herr-Hoyman)

    Subject: Re: FTP syntax

At 8:42 PM 3/7/94 -0500, Alan Emtage wrote:
>> I also think we could put it on the other end e.g.
>>
>> <url:ftp://ftp.path.net/one/two/three:binary>
>>
>> So that it's absence would indicate an old-stype URL, and that the
>> client was on its own at guessing what it was.
>
>That's fine with me... I'm not out to make the conversion more difficult.
>
>OK with everyone?
>
Are we sure the ':' is not a legal selector character? What about systems
where disks are noted with ':', is this going to pose a problem?

While I like the suggestion Mitra has (though I might like to see these
abbreviated to: dir,text,bin,tenex), I would again point out that we are
adding what amounts to metainfo in non-orthagonal ways in different
services. In particular, note how this contrasts with the gtype single
character for gopher, which is basically serving the same purpose.

- Next message: Fabio Metitieri: "Info Req."
- Previous message: Alan Emtage: "Re: FTP syntax"
- Maybe in reply to: Mitra: "FTP syntax"
- Next in thread: yandros@MIT.EDU: "Re: FTP syntax"
- Reply: yandros@MIT.EDU: "Re: FTP syntax"