Bertrand, when I say "multi tenancy at content" level, what I mean is that "multi tenancy at the content repository" level. Sorry for any confusion on that part. So we definitely want to separate the repositories for the individual tenants. The question is what is the best approach to do the same with minimum operational overhead.
Are you suggesting that we would have multiple Sling instances running (one for each tenant) and we will have some kind of Controller Sling instance that will take care of routing the request to appropriate Sling instance? -- View this message in context: http://apache-sling.73963.n3.nabble.com/Multi-tenancy-tp4036700p4037160.html Sent from the Sling - Users mailing list archive at Nabble.com.
