hi markus,
in my experience running different websites (for the lack of a better
term) in an environment is really a matter of isolation/separation
between the instances.
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 reach a greater isolation like running multi websites that
are completely separate i usually recommend to run things off of
different sling instances. even different jvm instances.
especially if you would like to have a degree of isolation where
a programming mistake in one website (let's say a "while(true){}")
does not impact the other websites i would definitely advocate separate
jvms.
really the cost of running a separate sling instance is a little bit of
disk-space and a few dozens of megabytes of heap.
regards,
david
2009/8/26 Alexander Klimetschek <[email protected]>:
> On Wed, Aug 26, 2009 at 5:58 PM, Markus Pallo<[email protected]> wrote:
>> The use case is each site has custom content which should not reflect to
>> others.
>>
>> And there is a news provider prvoviding news which both sites should use and
>> modification on these news should reflect on all sites immediatly.
>>
>> So probably we could have three content trees domain1, domain2, shared.
>
> Right, that's how it is typical.
>
>> If we have two or three different content trees in the same repository, how
>> to configure resource search path that the scripts will be found for the
>> corresponding content tree (site layout) ? The nodes have same
>> sling:resourceType.
>
> Well, they should have a different resource type then. Or, in cases
> where it makes sense, you can make the behaviour of scripts depending
> on the domain.
>
> But in general, in a CMS/webapp scenario, you want to reuse your
> scripts (or "components") with different content, not the other way
> around. Changing content is easier than developing new scripts and/or
> duplicating scripts.
>
> Regards,
> Alex
>
> --
> Alexander Klimetschek
> [email protected]
>
--
David Nuescheler
Chief Technology Officer
mailto: [email protected]
web: http://www.day.com/ http://dev.day.com
twitter: @daysoftware
