Jason E Bailey wrote
> Looking at the API I actually have something similar already written
> that uses a resource as a starting point and iterates down through the
> child resources to perform the query.
>
> In that manner it's agnostic as to what's providing the resource, as
> long as we are
Looking at the API I actually have something similar already written
that uses a resource as a starting point and iterates down through the
child resources to perform the query.
In that manner it's agnostic as to what's providing the resource, as
long as we are able to obtain the children of a
Steven Walters wrote
> I've seen this API (mentioned) before, and I don't understand why it
> has to get passed onto the ResourceProvider to handle the logic.
> It could instead be ResourceProvider agnostic, so always
> available/functioning no matter what providers are around/in use.
Really?
Hopefully other people chime in here, I've only had bad experiences
with utilizing queries and have often resulted in personally never
using them - so I always end up iterating/navigating myself.
Theoretically if you have a REALLY GOOD index then you may get some
similar performances, but if your
I've seen this API (mentioned) before, and I don't understand why it
has to get passed onto the ResourceProvider to handle the logic.
It could instead be ResourceProvider agnostic, so always
available/functioning no matter what providers are around/in use.
Continuing to depend on
if you know there are that few resources, then I say iterating would be
better performing than XPath / JCR-SQL2 queries.
This is primarily from past experience speaking in that queries have
generally turned out (often MUCH) slower than directly iterating if you
know what you're actually looking
Jason E Bailey wrote
> Which api proposal is that?
>
https://issues.apache.org/jira/browse/SLING-4752
Carsten
> --
> Jason
>
>
>
> On Thu, Jun 16, 2016, at 01:14 AM, Carsten Ziegeler wrote:
>> Steven Walters wrote
>>> The other providers sling manages in its codebase don't appear to
>>>
Which api proposal is that?
--
Jason
On Thu, Jun 16, 2016, at 01:14 AM, Carsten Ziegeler wrote:
> Steven Walters wrote
> > The other providers sling manages in its codebase don't appear to
> > get much
> > TLC, such as that they're all still using the older deprecated
> > ResourceProvider