[ndnSIM] The continuing Content Store saga (and question about NFD version being used)
Junxiao Shi
shijunxiao at email.arizona.edu
Sun Nov 6 07:40:55 PST 2016
Hi John
> - Okay, so here is what I understand: The Cs class is the *new *NFD
> content store class, correct?
>
> Yes. Everything in nfd:: namespace is NFD structs, including new NFD
content store.
>
> - In one of the e-mail exchanges, I was told that I could implement
> doAfterInsert( ) to control what was added into the content store (by
> allowing it in, then evicting it immediately if it didn't adhere to a
> custom set of requirements I could put in place.
> - There is no documentation in the NFD revision 3 for doAfterInsert,
> but I thought that the current version of ndnSIM uses this version of NFD?
>
> Source code and Redmine issue description (run git blame and find out
which commits modified the file, then look at Redmine) are your friends.
>
> - Do I obtain an instance of the Cs, or is all the work done with
> static methods? (e.g., ::find, ::insert, etc.)
>
> ns3::Ptr<ns3::ndn::L3Protocol> l3 =
ns3::ndn::L3Protocol::getL3Protocol(node);
nfd::Cs& cs = l3->getForwarder()->getCs();
Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20161106/1012546a/attachment.html>
More information about the ndnSIM
mailing list