> Multiple Plone sites for the same organisation sounds > inflexible to me. > It seems better if one organisation keeps everything in one > single site in order to share access to the same resources. > However, I'm not sure what happens to performance if it gets > really huge... plone.org is pretty big of course.... (but well-tuned)
plone.org is actually not well tuned at all ;-( it has been neglected for years and there should be a migration to latest Plone software Real Soon Now + extra tuning. I can imagine that one organization would have multiple plone sites. Mounting each Plone site as a separate mount point also gives you some extra knobs for tuning. Alan Runyan Enterprise Plone for the Windows Platform http://www.enfoldsystems.com/ > However, presumably the reason you want multiple Plone sites > is you have multiple clients? Perhaps then, you may want a > seperate Zope instance for each? Although this means many > Zope instances running, it can be easier to get your head > around, keeping data for different clients in seperate > compartmentalised places. Also you can do radically different > configurations of each Zope instance, if clients are > radically different in their usage. You might at some point > have different versions of Zope for different clients, but > then maintaining all this could be a headache. I guess its a > trade-off between simplicity and flexibility and the decision > needs to be carefully considered. > > Just a couple of thoughts....... > > Nick > > _______________________________________________ > Setup mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/setup > _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
