On 22.11.11 14:17, "Carsten Ziegeler" <[email protected]> wrote:
>This idea is about to provide a general approach for resource >checking. Noone prevents you from doing a virtual tree in the jcr >repository to check access of resources provided by other providers. >But that's an implementation detail which I don't want to require >upfront! I just expect that if Sling provides some simple ACL interfaces, people will start to implement them (w/o ever looking into what JCR ACLs they can have or implement) and only later detect & complain that it only works when you do everything in Sling's resource API. BTW: Where does Sling need resource checking? If something is not accessible = readable, it should simply not be returned from the resource provider (as JCR does). Cheers, Alex -- Alexander Klimetschek Developer // Adobe (Day) // Berlin - Basel
