[ http://issues.apache.org/jira/browse/JCR-169?page=comments#action_12316040 ]
David Nuescheler commented on JCR-169: -------------------------------------- > if you're AccessManager implementation reads the ACL's from repository > content > i assume it caches the ACL's for better performance. your AccessManager must > be therefore aware of changed ACL's and flush its cache accordingly. i would argue that this invalidation can easily work on top of the item modifications > btw: managing ACL's in content inevitably leads to chicken&egg kind > of problems and generally require nasty hacks. really? like what? i think managing acl "in content" is the about the best solution that i can come up with. > Make Jackrabbit clusterable > --------------------------- > > Key: JCR-169 > URL: http://issues.apache.org/jira/browse/JCR-169 > Project: Jackrabbit > Type: New Feature > Components: core > Reporter: Marcel Reutegger > Priority: Minor > > This jira issue discusses the technical implications on the current design of > Jackrabbit to introduce clustering. > Particularly the following areas require thorough investigation: > - SharedItemStateManager and its cache > - cache integrity > - cache design: look aside, write through? > - hook for distributed cache, interface? > - isolation level > - transaction integrity within Jackrabbit, interaction with transient > layer > - VirtualItemStateProvider > - same strategy as SharedItemStateManager? > - Search index > - single or per cluster node index? > - Observation > Please state more areas if needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
