Hi, My suggestion would be to (additionally or only) expose the current cluster node id in some way.
That way, oak-core (mainly hooks I guess; for example index implementations) can create properties and nodes that are known to not conflict with changes of other cluster nodes. Regards, Thomas On 04/03/14 15:37, "Chetan Mehrotra" <[email protected]> wrote: >FWIW DocumentNodeStore maintains a property '_modCount' on a per node >basis and it can possibly be exposed as part of NodeStore as a hidden >property. > >And that can be used to maintain the cache. DocumentNodeStore itself >internally relies on this to keep its caches in consistent state >Chetan Mehrotra > > >On Fri, Feb 28, 2014 at 7:52 AM, Jukka Zitting <[email protected]> >wrote: >> Hi, >> >> On Thu, Feb 27, 2014 at 4:46 PM, Tobias Bocanegra <[email protected]> >>wrote: >>> the current implementation allows to read all ACLs for a given >>> principal very efficiently at once with no false hasNode() accesses. >> >> Good point. >> >> To avoid has/getNode() misses (that can be expensive with MongoMK) in >> the proposed alternative, it would probably be a good idea to store a >> :hasPermissions flag property (or something similar) in each node with >> an ACL attached to it. Such a property could even be something like >> :permissionModCount in case in-memory caching (and cache invalidation) >> is still needed. >> >> BR, >> >> Jukka Zitting
