Hello, > On 5 May 2017, at 20:40, Robert Munteanu <[email protected]> wrote: >> I was wondering about this also WRT federated data store. > I think the high-level intent is the same for both - compose a single > {Data,Node}Store out of multiple sub-stores.
I also think that both implementations are conceptually similar and it’d be good if the name can reflect this. > The mechanisms might be different though, as the the NodeStore is > hierarchical in nature, while the BlobStore blob ids are opaque. > > Also I still maintain :-) that federated blob stores will work well > individually as they have no overall hierarchy to respect, while the > multiplexed node stores will have to be composed to create a meaningful > image. The thing is that the multiplexed node store works on the node store level and it doesn’t have any knowledge about JCR, trees, versioning, indexes, etc. - and it’s the same for all the implementations. The only things it cares about are node states and node builders. It’s true that the higher layers of Oak can use this abstraction to model paths, JCR nodes, version histories, etc. - but for the node store all of these things are hidden. We’re creating a node store that takes a number of other stores and exposes them together under the same interface - that’s why I think the federation is a good name. Since we’re working the mechanism implemented on the node store level, we should choose the name that makes sense for this level. Please notice that the higher layers and the various Oak subsystems that has to deal with the potential issues introduces by the multiplexing (eg. indexing or permissions) doesn’t reference the MultiplexingNodeStore at all - they only use the mounts. They don’t need to know what’s the node store implementation is, because mount info provider gives them all the information they need. In fact, sometimes it makes sense to configure the mounts with a simple Segment/Document Node Store, not the multiplexing one. Regards, Tomek -- Tomek Rękawek | Adobe Research | www.adobe.com [email protected]
smime.p7s
Description: S/MIME cryptographic signature
