On 25/06/2014 16:48, Jukka Zitting wrote: > The TreePermission interface is the key API here, and the way we've > designed it requires loading the nodes being accessed (see the > getChildPermission method). The current implementation of the API > actually *doesn't* strictly require the loading of the underlying > nodes, so we might be able to refactor the API to better accommodate > such indexes. > Never looked into the details so I'm most probably wrong.
Can't we do the ACL check lazily? Instead of the query engine looping through the nodes and check, if there's no need of doing so already (IE sorting), why not returning the set and then filter out the ACLs while the user load the node using the NodeIterator? D.
