My impression was that there was no notion of a "relative path"
when using
file: URLs... (though one would think that "file:relativePath"
with no
leading "/" ought to make sense...).
Any relative reference must be relative to something: its base.
Since the
"file" scheme provides the notion of a base, then relative
references can
be constructed under the file scheme. The original proposal was
RFC 1808,
which was obsoleted by RFC 3986 "Uniform Resource Identifier (URI):
Generic
Syntax". Section 4.2 "Relative Reference" is the relevant section.
<http://www.ietf.org/rfc.html>
Whether QuickTime on Mac OS X adheres to relevant RFCs is an entirely
different question.
The pertinent part of the rfc seems to be.
A relative reference that begins with two slash characters is termed
a network-path reference; such references are rarely used. A
relative reference that begins with a single slash character is
termed an absolute-path reference. A relative reference that does
not begin with a slash character is termed a relative-path
reference.
Stated as clearly as that it's hard to understand why there'd be any
inconsistent handling of file url's. It seems to be saying as
suggested above that no / at all is a relative-path. Intuitively I
was OK as long as it worked, with my file:// which I probably got
from some example. It's not too likely I'd make that up on my own.
But with user.dir you can again make it absolute and not have to
worry about any of this, when what's intuitive turns out not to be
correct, or my understanding of the rfc isn't completely clear.
Sometimes I try to keep it simple.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
