[Ndn-interest] How to get detailed CS lookup results?

[C-3 Comm Systems, LLC.]

When an interest arrives at an NDN node, the forwarding pipeline will search the CS and generate different triggers. According to the NFD Developer’s Guide and the comments in daemon/fw/strategy.hpp, either afterReceiveInterest is triggered if no matching data is found or afterContentStoreHit if a matching data is found.

Main Question — Is it possible, in a customized strategy, we can get more nuance CS look up results? 

A few additional but related questions are listed in the following to help explain our issue.

(Q1) What the default behavior of NDN implementation in the case that an interest only contains the prefix and there are more than one matching data found in the CS, returning the first one found or firing the afterReceiveInterest trigger indicating no match data found?

(Q2) When no match data is found, is it possible to tell the difference between these two cases: i) no name prefix matching; and ii) there are prefix matching but no exactly name matching.

(Q3) Is it possible to enumerate the longest prefix matching as the output of CS lookup? For example, an interest asks for /node/a/b/1, but in the CS, there are /node/a/b/2 and /node/a/b/3. We would like to have the strategy implementation get access to the list of {/node/a/b/2 and /node/a/b/3}, even though no exactly matching data is found. 

Thanks,
JC