[Ndn-interest] Disabling NDN's in-network caching
shijunxiao at email.arizona.edu
Thu Mar 19 09:33:44 PDT 2015
Yes, you may disable in-network caching by *setting ContentStore capacity
The relevant configuration option is tables.cs_max_packets in
However, this is an *unsupported configuration*.
- StatusDataset and Notification in NFD Management won't work before #
2182 <http://redmine.named-data.net/issues/2182>, which implies
nfd-status won't work.
- Remote prefix registration won't work before #1529
There could be other limitations as well.
On Thu, Mar 19, 2015 at 9:10 AM, Muhammad Hosain Abdollahi Sabet <
M.AbdollahiSabet at mail.sbu.ac.ir> wrote:
> In "A case for stateful forwarding plane", in the simulation part it said
> "Since we focus out evaluation on the effectiveness of stageful adaptive
> forwarding, we disabled NDN's in-network caching in the simulation." The
> question is: Is it possible to disable in-network caching in real NFD?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest