[Nfd-dev] How to treat ".." in an NDN URI?

Junxiao Shi shijunxiao at email.arizona.edu
Wed Aug 13 09:20:56 PDT 2014


Hi Beichuan


   1. visit ndn:/example/dir1/page1.htm
   2. page1 contains a link with href="../dir2/page2.htm"
   3. clicking this link navigates to ndn:/example/dir2/page2.htm

This procedure does not inevitably require ".." to be permitted in an
absolute URI. However, RFC3986 defines the resolution of both relative URI
and absolute URI to use the same procedure, therefore ".." is permitted in
absolute URIs as well.


Linking to relative URIs is useful in web development, because it allows an
author to create a web page or web application without first knowing the
absolute URI under which it would be hosted.
The alternative is to write absolute URIs everywhere, which is not
desirable by web developers.

Yours, Junxiao

On Sun, Aug 10, 2014 at 10:10 PM, Beichuan Zhang <bzhang at cs.arizona.edu>
wrote:

> can you give an example?
>
> On Aug 10, 2014, at 9:59 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>
> ndn protocol extension for Firefox needs relative URIs. The base URI used
> in resolution is Data Name without segment component.
>
> On Aug 10, 2014 9:56 PM, "Beichuan Zhang" <bzhang at cs.arizona.edu> wrote:
> >
> > This is complicate. In what scenarios do we need to use “up to a level”
> as an NDN name component?
> >
> > Can we treat ‘.’ and ‘..’ as is without the special meaning of “this
> level” and “up to a level”? I’m also fine with treating them as illegal
> name components.
> >
> > Beichuan
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140813/e49bb3a6/attachment.html>


More information about the Nfd-dev mailing list