Hi,
On 28/08/15 17:01, "Robert Munteanu" wrote:
>Hi Vikas,
>
>On Fri, 2015-08-28 at 20:28 +0530, Vikas Saurabh wrote:
>> Hi Robert,
>>
>> AFAIK, each node pushes paths that are changed by that node between 2
>> background updates.
>> Other cluster nodes mainly use it to generate external observat
Hi Vikas,
On Fri, 2015-08-28 at 20:28 +0530, Vikas Saurabh wrote:
> Hi Robert,
>
> AFAIK, each node pushes paths that are changed by that node between 2
> background updates.
> Other cluster nodes mainly use it to generate external observation
> events
> and cache invalidation due to changes by o
Hi Robert,
AFAIK, each node pushes paths that are changed by that node between 2
background updates.
Other cluster nodes mainly use it to generate external observation events
and cache invalidation due to changes by other nodes in the cluster.
So, yes it's useful only for cluster case.
I think M
Hi,
My current multiplexing prototype only handles multiplexing for the
NODES collection. However, upon a review it seems to me that the
JOURNAL collection is quite closely tied to the NODES collection.
By reading the code it looks to me like the only use it has is the
cache invalidation when cha
