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

Reply via email to