On Wed, Mar 13, 2013 at 10:09 AM, Felix Meschberger <[email protected]> wrote:
> ...Actually: It turns out that doing a ResourceProviderDecorator right is
> quite complex given
> the potential combinations of ResourceProvider extensions that might have to
> be captured.
> For now I would even go as far as to drop the ResourceProviderDecorator idea
> alltogether....
Interesting...I'm totally confused now, is that conclusion based on
on-list discussions that I missed?
I guess what we need is for whoever wants to work on this ("this"
being access control for non-JCR resource providers, which is IMO the
core topic here) to start by writing down use cases on which we can
agree, and we can then look at how to implement them.
As I said before, 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.
-Bertrand
