[Nfd-dev] Handling new content in app for pending interest in NFD

[Zhehao Wang]

Hi Wentao and John,

Is there any harm in it pushing the data out without knowing for sure if
> the
> Interest is still active?


I would think of this as a tradeoff between IO and processing capability,
if compared with our current approach of memoryContentCache with
in-application PIT. Both might be preferable given different application
scenarios.

As Dave suggested, using a repo implementation; or somehow (security
risks?) using the data unsolicited pipeline in nfd could be more ideal?

Thanks,
Zhehao

On Mon, Mar 30, 2015 at 11:11 AM, Wentao Shang <wentaoshang at gmail.com>
wrote:

>
>
> On Mon, Mar 30, 2015 at 11:08 AM Dehart, John <jdd at wustl.edu> wrote:
>
>>
>>  Is there any harm in it pushing the data out without knowing for sure if
>> the
>> Interest is still active?
>>
>
> Actually I don't think there is any problem with that either...
>
> Wentao
>
>
>>
>>  John
>>
>>   On Mar 30, 2015, at 1:05 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:
>>
>>
>>
>>
>>
>> On Mon, Mar 30, 2015 at 10:28 AM Burke, Jeff <jburke at remap.ucla.edu>
>> wrote:
>>
>>>
>>>  Hi folks,
>>>
>>>  We are facing this scenario in a few applications:
>>>
>>>  1) Interest received by NFD, passed to an application
>>> 2) Application not able to respond to interest, so interest stays in NFD
>>> PIT
>>> 3) Some time passes, but not enough for the Interest to expire
>>> 4) Application generates data (e.g., from a sensor reading) that would
>>> answer the Interest in the NFD PIT
>>>
>>>  Question: How does app know to inform NFD it has the data after step
>>> 4, and how should it do that?
>>>
>>>  - In this type of app, should it push the data unsolicited to the NFD
>>> and let it decide if there is something to do?
>>>
>>
>>  In my opinion, as long as the application is certain that the Interest
>> has arrived and is stored in NFD's PIT, it can just push the data out to
>> NFD.
>>
>>
>>
>>  How certain does it have to be?  There is a chance it could have
>> expired...
>> jeff
>>
>>
>>
>>
>>
>>
>>  Wentao
>>
>>
>>>  - Is it recommended to implement an application-level PIT so the app
>>> is sure this data is solicited?  (Why add *another* PIT?)
>>>
>>>  Thank you,
>>> Jeff
>>>
>>>  _______________________________________________
>>> Nfd-dev mailing list
>>> Nfd-dev at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>>
>>   _______________________________________________
>> Nfd-dev mailing list
>> Nfd-dev at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>
>>
>>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150330/311d1c49/attachment.html>