On 24.03.2013, at 14:09, Carsten Ziegeler <[email protected]> wrote:
> If we add support for calling this service from within the resource > resolver bundle, then the interface should definitely stay in the api. > We already have different packages with different services implemented > by different bundles, so I don't see why we should make a difference > here and put it into a different bundle. The crucial difference IMHO is that the sling API is meant for applications. The resource access security is a sling internal and optional one since for application code it is all transparent behind the resource resolver and resource API. Therefore it should go into a separate API bundle. Cheers, Alex
