Project

General

Profile

Actions
Copy link

Bug #1644

closed

ContentStore match algorithm does not consider scope

Added by Junxiao Shi almost 10 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Tables
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Steps to reproduce:

  1. on host A, use ndn-tlv-peek and ndn-tlv-poke to cause ndn:/localhost/A and ndn:/BBBBBBBBBB inserted into the ContentStore
  2. on host B, add a route ndn:/ toward host A with lowest cost
  3. on host B, execute ndn-tlv-peek ndn:/

Expected: ContentStore on host A returns ndn:/BBBBBBBBBB

Actual: ContentStore on host A returns ndn:/localhost/A, which is then dropped by outgoing Data pipeline due to scope violation

Actions
Copy link
 #1

Updated by Alex Afanasyev almost 10 years ago

I would say that this is correct behavior. Why would matching algorithm take into selection the scoping? Any matched data is good and it is problem of the client that he requested ambiguous data.

Actions
Copy link
 #2

Updated by Alex Afanasyev over 9 years ago

  • Status changed from New to Rejected

Again, this is correct behavior.

Actions
Copy link

Also available in: Atom PDF