2012/10/29 Alexander Klimetschek aklim...@adobe.com:
On 29.10.2012, at 18:02, Carsten Ziegeler cziege...@apache.org wrote:
And it's totally transparent and doesn't need any changes to the core.
Depends on what you define as core. The proposal definitely mentions a
change to the resource
And it's totally transparent and doesn't need any changes to the core.
Depends on what you define as core. The proposal definitely mentions a
change to
the resource resolver core.
No existing API will be changed. The changes are only under the hood. These
changes
only come to life if
Hi,
On Fri, Oct 26, 2012 at 10:43 AM, Mike Müller mike...@mysign.ch wrote:
...The main goal of this proposal is to provide a easy to use service in
Sling to restrict (or grant) access to resources for special use cases
(like giving access to some resources only between 8am and 5pm). The
On 30 October 2012 20:18, Bertrand Delacretaz bdelacre...@apache.org wrote:
Hi,
On Fri, Oct 26, 2012 at 10:43 AM, Mike Müller mike...@mysign.ch wrote:
...The main goal of this proposal is to provide a easy to use service in
Sling to restrict (or grant) access to resources for special use
I'm not sure about checkPermission with a String (or String[]). This
would imho only make sense if we see that we will have more
permissions in the future which I really don't see. And we don't need
an extension here as each additional permission would require changes
in the implementation to
On 30 October 2012 20:59, Carsten Ziegeler cziege...@apache.org wrote:
I'm not sure about checkPermission with a String (or String[]). This
would imho only make sense if we see that we will have more
permissions in the future which I really don't see. And we don't need
an extension here as
On Tue, Oct 30, 2012 at 10:59 AM, Carsten Ziegeler cziege...@apache.org wrote:
...I'm not sure about checkPermission with a String (or String[]). This
would imho only make sense if we see that we will have more
permissions in the future which I really don't see...
Thinking that no new types of
2012/10/30 Bertrand Delacretaz bdelacre...@apache.org:
...I also don't see a need to do it in the same way as JCR does - we
should do it what fits best in our resource api and what is the best
way to cover the use cases :)...
Of course, but some consistency wouldn't hurt either, I don't see
2012/10/30 Ian Boston i...@tfd.co.uk:
what about being able to check for a set of permissions in one go ?
As far as the proposal goes, there is no need for this as usually
always exactly one permission is checked.
Carsten
So I would go with the separate methods - we could provide an
On 30.10.2012, at 08:43, Mike Müller mike...@mysign.ch wrote:
And it's totally transparent and doesn't need any changes to the core.
Depends on what you define as core. The proposal definitely mentions a
change to
the resource resolver core.
No existing API will be changed. The changes
I like this proposal as it is really generic and allows for some very
interesting use cases like denying access to resources for a given
time or allowing only access if the user has paid for the content or
whatever :)
And it's totally transparent and doesn't need any changes to the core.
As
On 29.10.2012, at 18:02, Carsten Ziegeler cziege...@apache.org wrote:
And it's totally transparent and doesn't need any changes to the core.
Depends on what you define as core. The proposal definitely mentions a change
to the resource resolver core.
On 26.10.2012, at 10:43, Mike Müller
On 26.10.2012, at 10:43, Mike Müller mike...@mysign.ch wrote:
The main goal of this proposal is to provide a easy to use service in
Sling to restrict (or grant) access to resources for special use cases
(like giving access to some resources only between 8am and 5pm). The
service should be
13 matches
Mail list logo
