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 other nodes in the cluster. > > So, yes it's useful only for cluster case.
Thanks for the reply. If it's cache invalidation only, I would not be bothered ( for now ). If it's propagation of external observation events I would be bothered quite soon :-) > I think Marcel and Stefan can judge better if this needs to be looked > at > immediately. Ack. Thanks, Robert > > -Vikas > (sent from mobile) > On 28-Aug-2015 8:06 pm, "Robert Munteanu" <[email protected]> wrote: > > > 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 changes happen between cluster nodes. Is > > that > > correct? > > > > If it is I will be able to delay looking into the Journal > > consistency a > > bit, but if it can lead to hard-to-debug errors later I'd rather > > look > > into it now. > > > > Thanks, > > > > Robert > >
