[Ndn-interest] application scenario

[Lan Wang (lanwang)]

Yes, I want to synchronize only part of the data.

I can still use ChronoSync to get updates for all the prefixes and only retrieve the ones I'm interested in.  This will work, but it would be nice if I don't have to maintain state for all the name prefixes. 

Lan

On Oct 21, 2014, at 4:51 PM, Christos Papadopoulos <christos at CS.ColoState.EDU> wrote:

> Sounds like you need the ability to synchronize prefixes, not the entire root.
> So you would like to synchronize /a and /b.
> 
> Christos.
> 
> On 10/21/2014 02:35 PM, Lan Wang (lanwang) wrote:
>> Hi there,
>> 
>> Suppose I have a node A that has limited memory.  It wants to synchronize partial data with other nodes (B and C).    The other nodes are fully synchronized with each other (they use ChronoSync).   Node A wants to get updates whenever the other nodes have more recent versions of the data it has, but the other nodes do not know what A has.  What's the best way to design this application?  Ideally we don't want A to specifically sync with one particular node (B or C).
>> 
>> Here's an illustration:
>> 
>> * Node A has:
>> 
>> - /a/v1
>> - /b/v1
>> 
>> * Node B and C have:
>> 
>> - /a/v1
>> - /b/v2
>> - /c/v3
>> 
>> Ideally A should get update about /b/v2, but not /c/v3 as it's interested in /b, not interested in /c.
>> 
>> We don't want to run ChronoSync on A, as it doesn't have the space for all the data and it is not interested in all the data either.
>> 
>> Lan
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>> 
> 
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest