2011/11/23 Mike Müller <[email protected]>: > I think the discussion here is missunderstood. It's neither about > to redefine existing ACLs nor about reinventing something already > existing. It's just about introducing hooks or entrypoint to let > developers define some other access controlling rules if needed. > Sling will NOT have to deal with permissions or policies, users and so > on. That's all up to the developer which want's to use the hooks. > So if you're are fine with the ACLs from JCR, you don't have to > change anything, if you are not, this would give you the chance > to solve your problem (like my example to give access to a > resource from 8.00 to 17.00). > So > It would help not only for special rules like the one above, it would > also help to handle access controlling on resources which are provided > from another resource provider than JCR, like the file system provider, > where no access controlling can be attached today. > And again: If someone is fine just with the JCR resource provider and > the ACLs, nothing will be more complicated after the introduction of > the hook than before. > Exactly, thanks Mike :)
And keep in mind that the intend of Sling is to provide a framework to create a resource oriented architecture. This is not tied to jcr. We already have other providers (file and bundle) and in the near future we will have additional providers for other data storages. Regards Carsten -- Carsten Ziegeler [email protected]
