when looking in the wiki i found another page [1] with some thoughts on multi tenancy from a mailing list discussion from february [2]
from this i get we have two quite different scenarios although they have a shared part: * the "fully isolated tenant" scenario - tenants are fully isolated and have their own script (overlay) path, own users, own i18n etc. - as described in [1] - the existing tenant implementation targets on this scenario as well, but does currently fulfill only part of the requirements from [1] * the "manage multiple tenants" scenario - a set of users (editors, admins etc.) manages a set of tenants with n-to-m relation between users and tenants - providing script overlays and admin separation is not that important, but configuration and content separation it think both scenarios can be handled with a single (flexible/customizable) implementation, but both have their own complexities not relevant for the other. so when starting a wiki page we have to respect both scenarios. stefan [1] https://cwiki.apache.org/confluence/display/SLING/Multitenancy+Support+Integration [2] http://apache-sling.73963.n3.nabble.com/Tenant-Implementation-in-Sling-td4031217.html#none >-----Original Message----- >From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] >Sent: Monday, August 11, 2014 3:32 PM >To: Bertrand Delacretaz >Cc: dev >Subject: Re: [RT] Multi Tenancy > >On Mon, Aug 11, 2014 at 3:29 PM, Bertrand Delacretaz ><bdelacre...@apache.org> wrote: >> ...I suggest creating a page under >> https://cwiki.apache.org/confluence/display/SLING for multi-tenant use >> cases and definitions... > >There's already >https://cwiki.apache.org/confluence/display/SLING/Multitenancy+Support >but as Carsten says we do have a tenant API now. Like Stefan I'm just >suspecting people have different ideas about what multi-tenancy means, >so having use cases would help. > >-Bertrand
