Hi Stefan, thanks for putting this together. While I agree that the requirements are different for the 2 scenarios, I'd rather see the multi-site scenario as a subset of virtual hosting. Tenants in virtual hosting could be structured internally as a multi-site as well.
I also think that in the virtual hosting scenario there are requirements for users to access multiple tenants. Think of agencies working on behalf of multiple customers. I'm not sure I understand the definition that tenants are defined upfront in virtual hosting. They can be created dynamically at run time. Alex On Tue, Aug 12, 2014 at 12:43 PM, Stefan Seifert <sseif...@pro-vision.de> wrote: > i created a first draft of a wiki page where i tried to collect the > different views of and requirements for multitenancy of the recent > discussions: > https://cwiki.apache.org/confluence/x/So2uAg > > i coined new names for the two scenarios "Virtual Hosting" and "Massive > Multi Site" > > we should decide first which of the requirements we can target in a first > phase, and which are more complex or even not solvable within the current > architecture. and - of course - what is already fulfilled by the current > sling tenant implementation. > > my interest is currently primary in the "massive multi site" scenario, and > especially the configuration part in it. > > stefan > -- Alexander Saar Mobile: +49.172.8280280 E-Mail: alexander.s...@gmail.com
