[ndnSIM] Forwarder's onIncomingInterest
jpbaugh at umich.edu
Tue Jun 13 05:32:33 PDT 2017
What is interesting to me is when I obtain the Forwarder object from say,
one of the consumers, it seems that the method onIncomingInterest is called
for however many times the interest would be sent (e.g., 300 times for rate
of 10/sec for 30 seconds in simulator.)
It is at the router (my node 1) that it only appears to call the
onIncomingInterest once there.
So would a solution be to set the size/limit of content stores of the
consumers to 0? Or do I need a custom policy to purge their CSs so they
keep sending the same interest?
I'm unclear what you mean by interest aggregation in this situation.
My ultimate goal is to be able to have the router receive many interests
for various content objects. The router tracks frequency per face for each
content object requested.
On Jun 13, 2017 7:02 AM, "Junxiao Shi" <shijunxiao at email.arizona.edu> wrote:
> I re-read the NFD documentation and it does seem to suggest that
> onIncomingInterest is called for all incoming interests (and localhost
> stuff too)
> Anyway, I'm only detecting a single incoming interest entering on faces
> into the router for content, when it should be around 300 times (10 / sec.
> For 30 seconds, simulated)
If it is a management Interest (under /localhost/nfd prefix), check your
If it is an application Interest, and if you are sending the same Interest
over and over from the consumer apps as mentioned in
http://www.lists.cs.ucla.edu/pipermail/ndnsim/2017-June/003870.html , this
is caused by Interest aggregation and Data caching at the consumer NFD.
When multiple consumer apps send the same Interest, only one is forwarded
to the router, and the Data will be returned to all applications.
Afterwards, the Data is in the consumer NFD's cache and will be used to
satisfy future Interests of the same name.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ndnSIM