[Nfd-dev] Fetching data that NFD has overheard

Ashlesh Gawande (agawande) agawande at memphis.edu
Fri Aug 31 11:53:37 PDT 2018


https://github.com/named-data/NLSR/blob/057005460ef462dd298126312650999bf22f8425/src/nlsr.cpp#L664


Ashlesh

________________________________
From: Nfd-dev <nfd-dev-bounces at lists.cs.ucla.edu> on behalf of Spyridon (Spyros) Mastorakis <mastorakis at cs.ucla.edu>
Sent: Friday, August 31, 2018 1:50:08 PM
To: Junxiao Shi
Cc: <nfd-dev at lists.cs.ucla.edu>
Subject: Re: [Nfd-dev] Fetching data that NFD has overheard

Hi Junxiao,

thank you for your response.

I tried but the Interest is getting dropped right away, because local fields are not enabled. How can I enable local fields for a unix stream transport? (I guess by default a local application is attached to the local NFD through such a transport, right?)

Thanks,
Spyros

On Aug 30, 2018, at 8:54 PM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:

Hi Spyros


The straightforward way would be to add the app's face to the incoming faces of the Interest’s PIT entry, so that NFD forwards the data to the application when it overhears the data transmission. Is there a way to do that (or a way to achieve similar functionality) from the application code without modifying the source code of NFD?

Whenever your app needs to receive a piece of Data, you express an Interest.
If you don’t want the Interest to be transmitted, set NextHopFaceId=255 so it’s forwarded to the NullFace and effectively dropped.

Yours, Junxiao

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20180831/d4a37e5e/attachment-0001.html>


More information about the Nfd-dev mailing list