[Ndn-interest] [EXT] NFD-out-of-the-box

Teng Liang philoliang at email.arizona.edu
Wed Jan 5 20:34:56 PST 2022


Hi Ahmed,

Yes, you are right. sendData should be used instead of sendDataToAll.

We found the exact same bug and the solution as you described, but forgot
to update it on Github. Thank you for your feedback!

Best regards,
Teng

On Thu, Jan 6, 2022 at 12:23 AM Ahmed Taffal via Ndn-interest <
ndn-interest at lists.cs.ucla.edu> wrote:

> *External Email*
> Hi everyone,
>
> I am using NFD-out-of-the-box and its self-learning strategy. I found when
> I send a discovery interest to another node, and that node has the content
> (without PA) in its CS, the function asyncProcessData(pitEntry,
> ingress.face, data) will be called.
> This function will call sendDataToAll(pitEntry, *inFace, data) to get the
> list of pit entry in-records. As it is known, when the pit entry has a CS
> hit, it will not have any value in the in-record table and so the
> sendDataToAll function will not send the data to the downstream.
> I tried to retrieve content from the Producer's CS using ndncatchunks and
> I am not getting any content chunk.
> However, in the asynProcessData function, I replaced the sendDataToAll
> with sendData and the data from the CS was retrieved successfully.
> Is it true that the sendData function is the correct one to use after CS
> hit and not the sendDataToAll?
>
> Best Regards,
> Ahmed.
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20220106/ce49ff1c/attachment.html>


More information about the Ndn-interest mailing list