hi markus, it was brought to my attention, that i forgot to mention the sharing of content amongst websites as a use case so i would like to clarify the below statement a little bit more in detail...
> if you assume that you have separate content trees but would like to > share the applications or the security (the users) it is perfectly > feasible to run things off of one sling instance. if you want to share "content" (in the broader sense) amongst sites, including "website content", "apps", "config", "users" or anything else stored in the repository, you possibly want to use one single sling instance. as a rule of thumb i would say that the more you share, the higher the chances of a shared sling instance. isolation makes sense in the "hosting" usecase where you have different customers that (must) share nothing. regards, david
