On Wed, Mar 13, 2013 at 10:38 AM, Felix Meschberger <fmesc...@adobe.com> wrote: > Am 13.03.2013 um 10:18 schrieb Bertrand Delacretaz:
>>...adapting the JCR permissions model to Sling >> resources would be my favorite way by far - that model is known to >> work and we are familiar with it, no need to reinvent too many wheels. > > If we can implement Mike's new service ontop of JCR, I think we are fine, > right ? I just > don't want to nail non-JCR ResourceProviders onto JCR directly. That would be > counter-productive.... Absolutely agree - what I mean is that if we need to design an access control mechanism for non-JCR resource providers, let's reuse the JCR permissions *model* as much as possible. Without having dependencies to JCR, but just reusing those ideas that are known to work in there, and should be familiar to Sling developers who use JCR. -Bertrand
