[
https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593538#comment-13593538
]
Alexander Klimetschek edited comment on SLING-2698 at 3/5/13 4:25 PM:
----------------------------------------------------------------------
In light of angela's comments, let me repeat that I basically have the same
concern as mentioned on the list before (
http://markmail.org/message/mby7qfrwdilwyf5t ):
I think it might make sense for Resource implementations that don't have their
own access control mechanism. If you already have one (like with JCR), it
shouldn't be used/promoted, as that would just create confusion (why can't I
configure this hard-coded rule etc.).
So if there is a need for that, I'd look for not adding this service to the
sling resource core but allow it to be implemented in some kind of a wrapping
resource provider, which you could hook in like any other resource provider.
Becauser then people will get the idea to use it together with e.g. JCR ACLs
and run into problems later which then fall back onto sling etc.
was (Author: alexander.klimetschek):
In light of angela's comments, let me repeat that I basically have the same
concern as mentioned on the list before
(http://markmail.org/message/mby7qfrwdilwyf5t):
I think it might make sense for Resource implementations that don't have their
own access control mechanism. If you already have one (like with JCR), it
shouldn't be used/promoted, as that would just create confusion (why can't I
configure this hard-coded rule etc.).
So if there is a need for that, I'd look for not adding this service to the
sling resource core but allow it to be implemented in some kind of a wrapping
resource provider, which you could hook in like any other resource provider.
Becauser then people will get the idea to use it together with e.g. JCR ACLs
and run into problems later which then fall back onto sling etc.
> Add a minimal resource access gate
> ----------------------------------
>
> Key: SLING-2698
> URL: https://issues.apache.org/jira/browse/SLING-2698
> Project: Sling
> Issue Type: New Feature
> Components: ResourceResolver
> Reporter: Mike Müller
> Assignee: Mike Müller
> Fix For: Resource Resolver 1.1.0
>
> Attachments: resource-resolver-wrapper.patch
>
>
> Adding a minmal resource access gate as discussed in [1].
> First step is to define the API interface and a minimal implementation which
> allows to define READ access (rest of CRUD can follow later)
> [1] http://markmail.org/thread/4ctczoiy533tquyl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
