On 2013-03-13 21:24, Boris Zbarsky wrote:
On 3/13/13 4:23 PM, Julian Reschke wrote:
Under RFC 3986, it would resolve to
jar:http://example.com/Bar.class
If you assume that this is a hierarchical scheme and that the hierarchy
is in some particular place, no? Why is that assumption being made?
No such assumption was made. Just following the algorithm in the spec.
Looks like a broken scheme to me.
I'm not going to try to claim jar: is a wonderful thing. It is what it
is. It needs to not break.
Is it used outside Java applet scenarios?
BTW: this shows why formal registration and review of URI schemes is a
*feature*.
Best regards, Julian
