[Nfd-dev] NDN-RTC poke Data to CS

[Beichuan Zhang]

How about this workaround?

The browser app sends data to a proxy app on a remote node, the proxy has a local face to NFD and pushes data via this face. Since the data come from a local face, NFD will save this unsolicited data in CS.

Beichuan

On Mar 18, 2014, at 10:44 PM, Burke, Jeff <jburke at remap.ucla.edu> wrote:

> Hi Beichuan,
> 
> Thanks for the further explanation.
> 
> We would like to run the ndnrtc on NFD as an initial test – should we look for this functionality in the repo or try to provide it in the library?  (or both?)
> 
> thanks,
> Jeff
> 
> 
> From: "bzhang at cs.arizona.edu" <bzhang at cs.arizona.edu>
> Date: Tue, 18 Mar 2014 22:38:31 -0700
> To: Junxiao Shi <shijunxiao at email.arizona.edu>
> Cc: "ndn-app at lists.cs.ucla.edu" <ndn-app at lists.cs.ucla.edu>, Peter Gusev <peter at remap.ucla.edu>, <nfd-dev at lists.cs.ucla.edu>
> Subject: Re: [Nfd-dev] NDN-RTC poke Data to CS
> 
> In my opinion, caching unsolicited data or not should be the choice of each individual node; nothing in the architecture or protocol prevents that.
> 
> What Junxiao said is probably what the first release of NFD will have. 
> 
> Beichuan
> 
> On Mar 18, 2014, at 7:57 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
> 
>> Hi Peter
>> In seminar slides you mention that the RTC application in browser may poke Data to a remote forwarder.
>> I want to inform you that NFD will not admit any unsolicited Data from non-local face. NFD will admit unsolicited Data from local face, but they will be the first to get evicted when CS is full.
>> You should insert Data into a  repository instead.
>> Yours, Junxiao
>> _______________________________________________
>> 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/20140318/524d035d/attachment.html>