Hi, I was recently working on some code which used ResourceResolver#findResources to get an Iterator of Resources based on a relatively simple query.
Unfortunately, due to performance concerns, I ended up having to switch to the JCR API to specify a limit. In order to make the querying in Apache Sling more useful, would it make sense to: 1. Add support for "QueryOptions" as an additional parameter to an additional findResources method. This would be a Map of options to be passed to the underlying query engine which would (if supported) influence the query executed. We could then create a few constants for common parameters such as limit and offset. 2. Expose the org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator helper class. This class can be used to easily wrap a NodeIterator as an Iterator<Resource> however as it is in the internal package it cannot be referenced from other bundles. Any thoughts or concerns regarding these two proposals? Regards, Dan
