# Re: Unresolved URL issues

Scott W Brim (swb1@cornell.edu)
Fri, 18 Mar 1994 23:38:16 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alan Emtage: "Re: URN specification"
- Previous message: Daniel W. Connolly: "Re: Unresolved URL issues"
- Maybe in reply to: Alan Emtage: "Unresolved URL issues"

    Message-Id: <199403190438.XAA13629@postoffice3.mail.cornell.edu>

    Date: Fri, 18 Mar 1994 23:38:16 -0500

    To: uri@bunyip.com

    From: Scott W Brim <swb1@cornell.edu>

    Subject: Re: Unresolved URL issues

Folks, I admit I've been skipping lightly through the mail on FTP URLs,
but ... why does the URL have to model the file system of the server?
I have only touched the web for a matter of months but I've been
designing protocols for years, and it is always a good idea to decouple
the protocol used to express a wish from the mechanism by which that
wish is fulfilled. Let the URL contain symbols which signify a
directory change, say "/", and let the action to be taken on such a URL
be completely the server's business, for example whether to do multiple
CWDs or not. If this is a clue-challenged newbie attitude, just don't
reply.

Thanks ... Scott

- Next message: Alan Emtage: "Re: URN specification"
- Previous message: Daniel W. Connolly: "Re: Unresolved URL issues"
- Maybe in reply to: Alan Emtage: "Unresolved URL issues"