Hi Jose, well I guess that depends a bit on what your environment is. We at Hippo have used mulitple project -> 1 cocoon in the past, but switched to using 1 cocoon instance per project.
The problem with multiple project in 1 cocoon is that if one project causes your server to fail it will drag down all the others. Also with updates it can be more easy to update only one application instead of shutting down all project because 1 project needs a new dependency. I guess it's more a personal taste, but a good topic IMO to see how people handle their cocoon environments. Regards, Jeroen -----Original Message----- From: José Miguel Vieira [mailto:[EMAIL PROTECTED] Sent: Mon 3/31/2008 11:37 AM To: [email protected] Subject: Multiple or single cocoon instances Hello, At the moment we have several cocoon projects, about 20 or so, running inside the same cocoon, version 2.1.10. Is this the best way to do it, or would it be better to have one cocoon instance per project? Thanks, Miguel --- José Miguel Vieira Centre for Computing in the Humanities King's College London 26 - 29 Drury Lane WC2B 5RL London Email: [EMAIL PROTECTED] Tel: +44 (0)20 7848 1242 Faxl: +44 (0)20 7848 2980 http://www.kcl.ac.uk/cch/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
