[ndnSIM] storing the name of content

fatemeh goudarzi f.goudarzi at mail.sbu.ac.ir
Mon Nov 21 10:40:32 PST 2016

Hi Muhammad,
A subset of CS information should be saved in another data structure. This information is not only related to the node itself but name of cached contents in some nodes (some nodes,not all of them) must be saved in this structure. These nodes send an interest in order to inform each other about their content's name with specific prefix. The receiver nodes of this interests have to divide the content's name and save it to their data structure.
From: Muhammad Hosain Abdollahi Sabet [mhasabet at gmail.com]
Sent: Monday, November 21, 2016 12:08 AM
To: fatemeh goudarzi
Cc: ndnsim
Subject: Re: [ndnSIM] storing the name of content

Hi Fateme,

If I've guessed correctly, you are going to store a subset of CS information(the name of cached contents), in another data structure(apparently some std::set) on nodes. Well, for previous cached contents you should read their names from CS. For future ones, you may catch them (of course with their names) at the time of being cached in Forwarder. It seems to me nfd is where you'd better implement it, unless you don't want all of your nodes have such information stored. Could you elaborate more? How are nodes going to inform others of this information? Is it something like exchanging FIB info in a routing protocol?


خندان باشید
با تشکر

On Wed, Nov 9, 2016 at 2:09 AM, fatemeh goudarzi <f.goudarzi at mail.sbu.ac.ir<mailto:f.goudarzi at mail.sbu.ac.ir>> wrote:


I want that some nodes inform each other (immediately after caching the content) that each one has cached what content and store its name in nodes. If I use set data structure to store the name of content in each node, is it preferred to implement this set in an application or in NFD?
I appreciate any help.


ndnSIM mailing list
ndnSIM at lists.cs.ucla.edu<mailto:ndnSIM at lists.cs.ucla.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20161121/a297c629/attachment.html>

More information about the ndnSIM mailing list