On Mon, Nov 12, 2012 at 10:55 AM, Felix Meschberger <[email protected]> wrote: > ...The current idea is just: > > * A ResourceResolver representing a user (just like JCR Session does) can be > adapted to a Tenant to which the user "belongs". > * A Resource can be adapted to a Tenant under the assumption that the > respective Resource belongs to one of the Tenant's data areas in the > repository. > ...
I looked at the SLING-2656 code and the way I see it this is just an Adapter that provides the properties of a node, wrapped in a read-only Tenant interface, based on the current request's Authorizable path. That's probably useful, but calling this multi-tenancy support is misleading IMO - as Julian's message shows, people would usually expect much more from that, and it doesn't look like we're able to provide that with Sling currently, by far. My suggestion is then just to call this the Tenant API, and refrain from speaking of multi-tenancy to avoid inflated expectations. It's just an embryo of multi-tenancy. (not to downplay Amit's contribution - thanks very much for that, we just need to agree on the right "marketing" IMO) -Bertrand
