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? How? Carsten > > Continuing to depend on ResourceProviders for such functionality > (especially a query language this basic that could just be done > through standard Sling resource visitation/navigation/iteration) > doesn't seem all that beneficial, it just seems to add more complexity > to the ResourceProviders that already have enough complexity as they > are. > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
