file:/ vs file://<host>/ vs file:///
kevin.krammer at gmx.at
Thu Nov 4 21:05:51 EET 2004
On Thursday 04 November 2004 19:42, Alexander Neundorf wrote:
> On Thursday 04 November 2004 18:59, Daniel Veillard wrote:
> > On Thu, Nov 04, 2004 at 12:18:57PM -0500, Avery Pennarun wrote:
> > > On Thu, Nov 04, 2004 at 11:35:54AM -0500, Daniel Veillard wrote:
> > > > Either you have an authority or not. In any case you cannot have
> > > > file://foo
> > > >
> > > > Now what semantic would you provide for
> > > > file:/foo ?
> > >
> > > file:/foo == file://localhost/foo
> > >
> > > Everybody already knows this.
> > it's not in any spec, sorry ...
> At least approx. 50% of the linux desktop users know this (KDE supports
> file:/ foo).
If I understand this  correctly, KDE will either support both or switch to
the other form.
> I don't think "normal" users will understand why they have to put 3 slashes
> infront of the path. And I don't think file can ever be combined with
> anything else than localhost, so it's redundant.
I think the host part is important when doing DnD and clipboard stuff.
More information about the xdg