Re: Internal Filename Representations (was Re: Summary of I/O related RFCs)

Jarkko Hietaniemi <[email protected]> writes:
>On Fri, Aug 11, 2000 at 02:16:31AM -0700, Nathan Wiger wrote:
>> [cc'ed on internals as FYI]
>> 
>> > =item 36 (v1): Structured Internal Representation of Filenames
>> 
>> I think this should be discussed a good amount. I think URIs are cool,
>> but too much trouble for simple stuff. I don't want to have to write
>> "file:///etc/motd" everytime I want to address a file. Too cumbersome.

URI's have thought of that already - you can have a "relative URI" with 
a parent specified. 

We would have a default parent of file://localhost/$PWD

>
>The (vague) idea wasn't that "everything shall be an URI".  It was
>the other way round: "the representation should be generic enough so
>that also URIs could be handled".  In other words: things like
>the protocol, the port number, the username, the password, could
>be part of a "file spec".

Quite.


-- 
Nick Ing-Simmons