On 10/06/15 11:08, "Robert Munteanu" wrote: >So you would see a CachingDocumentStore which does both caching and >multiplexing (if needed) ?
no, multiplexing does not belong there. IMO this would be implemented on top of it. > If that is the case, my question still stands - how do we approach >the document key semantics? maybe CachingDocumentStore is misleading and we would rather name it HierarchicalDocumentStore, which also implements caching and leverage hierarchical information for invalidation as needed. HierarchicalDocumentStore would extend DocumentStore and introduce new methods for NODES collection related operations with the proposed DocumentKey (or similar). multiplexing would be a HierarchicalDocumentStore implementation as well and delegate to other HierarchicalDocumentStores. >Do we formalise the fact that it has a depth:path format? this would be part of the HierarchicalDocumentStore and the methods it defines. Regards Marcel
