[ndnSIM] Using the setExpiryTImer

Xinyu Ma bitmxy at gmail.com
Sat Nov 24 09:21:14 PST 2018

Hello, Pradhan

I’m sorry I don’t understand why you want to extend the PIT entry’s lifetime and what you mean by “data response other than the first one”.
NDN follows One-Interest-One-Data, so the PIT entry should be deleted after receiving the data.
You can send another Interest if you still want the PIT entry to be there.

Xinyu Ma.

> On Nov 24, 2018, at 6:20 AM, Ashish Pradhan <ashishpradhan1162 at gmail.com> wrote:
> Hi all,
> I am trying to use the setExpiryTimer to extend the PIT entry's lifetime. However the data response other than the first one is not being forwarded back to the consumer. I have included the setExpiryTimer in the beforeSatisfyInterest function as follows:
> "NFD_LOG_DEBUG("beforeSatisfyInterest pitEntry=" << pitEntry->getName() <<
>                 " inFace=" << inFace.getId() << " data=" << data.getName());
>   this->Strategy::setExpiryTimer(pitEntry, ndn::time::milliseconds(100));"
> Is there any thing that needs to be added?
> After looking at the sendData function there is this line "pitEntry->deleteInRecord(outFace);". If it is deleting the inRecord how does the setExpiryTimer help to preserve the entry?
> Best regards,
> Ashish Pradhan
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim

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

More information about the ndnSIM mailing list