[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: KURL bugs
From: Waldo Bastian <bastian () ens ! ascom ! ch>
Date: 1999-06-18 9:01:10
[Download RAW message or body]
Nicolas Brodu wrote:
> IIRC, the RFC stated that a URL was basically <scheme>:<scheme part> and
> then proposed "standard schemes".
> IMO, the "file" protocol introduced in the RFC was adapted for accessing
> files over the internet, but this shouldn't prevent us from making our
> own file "scheme", much more adapted to local files.
> Anyway, why not accept both file:/localFile and
> file://localhost/localFile ?
I patched KURL (HEAD branch only, I don't have a working 1.1 branch)
to include the following:
The URL
file://localhost/path/file
is handled the same as
file:///path/file
and the same as
file:/path/file
All URLs above return an empty host() and url() returns "file:/path/file".
The URL
file://somehost/path/file
is handled depending on the setting in kioslaverc.
The default is to return an empty host() and "//somehost/path/file" in path().
Optionally the setting in kioslaverc can specify a "protocol". In this case
the URL will return "protocol" as protocol(), "somehost" as host() and
"/path/file" as path().
Example: If in kioslaverc "smb" is specified, the URL
file://somehost/path/file
will return
"smb://somehost/path/file" as url().
Cheers,
Waldo
We should. I would also like to accept
file://some_host_name/path/filename and then map it (based on configuration)
to either
smb://some_host_name/path/filename
or
nfs://some_host_name/path/filename.
or
file://some_host_name/path/filename
(but with "//some_host_name/path/filename" ending up in the path)
Which is usefull when the system's "open()" call understands what is meant with
"//some_host_name/path/filename". (I believe some automounters use this)
Cheers,
Waldo
--
KDE, A New Millenium, A New Desktop http://www.kde.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic