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

[Giovanni Pau]

Hi All, 

Junxiao, thanks for the clarification, in such case we will just add our code on step 2. I’m just concerned about the maintenance of the code. I would avoid pretty much at all costs to have different separate code-trees this would make maintenance an hell. That is why i’m much more in favor of adding some complexity in the code to allow flexibility, this is for Caching unsolicited data as well as lifetime etc. 

In other words we may have  the function there that  depending on a number of parameters (i.e. the Face is V2V/V2I) deciders if unsolicited data is to be stored in the CS or not. I agree with the separate design from the CS this will allow a lot of experimenting with different CS strategies etc. 

Thanks
g. 

On Mar 22, 2014, at 6:40 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:

> Dear folks
> 
> The design is:
> 	• Incoming Data pipeline decides whether a Data is unsolicited or not.
> 	• A function decides whether an unsolicited Data CAN be admitted.
> 		• Currently, this function returns true if incoming face is local.
> 		• Replacing this function allows for alternate behaviors.
> 		• This function SHOULD NOT be part of CS policy (which governs the replacement of cached Data). It is a policy in forwarding, not in CS.
> 	• If allowed by the function in step 2, the Data is given to CS.
> CS policy decides whether to admit the Data based on available space, and also decides which Data to evict in case CS is full.
> 
> Yours, Junxiao
> _______________________________________________
> Ndn-app mailing list
> Ndn-app at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-app