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

[Gusev, Peter]

Hi Junxiao,

Thanks for your concerns.
I should have mentioned this on the slides - I plan to have an "in-memory" content store in the app and handle incoming interests for the segments manually, so I do not need to rely on the presence of local daemon. However, with the scheme when an instance of a forwarder will be inside the browser, this scheme may change and allow app to poke data straight into it. Though it's unclear now.
As the main reason why we decided to avoid using repository - is the access time to the data, which is apparently larger then the access to the "in-memory" CS.

Thanks,

--
Peter Gusev
peter at remap.ucla.edu<mailto:peter at remap.ucla.edu>
+1 213 5872748 (USA)
+7 916 4434826 (Russia)
+37 259 226448 (in case any other number is unavailable)
peetonn_ (skype)

On Mar 18, 2014, at 7:57 PM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto: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

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