Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 24972 invoked from network); 6 Jul 2000 12:25:21 -0000 Received: from sundn.pb.teuto.net (HELO viruswall.ynes.de) (212.8.194.130) by locus.apache.org with SMTP; 6 Jul 2000 12:25:21 -0000 Received: from 10.10.1.10 by viruswall.ynes.de (InterScan E-Mail VirusWall NT); Thu, 06 Jul 2000 14:24:52 +0200 (Westeuropaeische Sommerzeit) Received: from hw0230 (fw-dmz.ynes.de [10.10.1.1]) by mail.ynes.de (8.9.3/8.9.3/NoSpam) with SMTP id OAA25743 for ; Thu, 6 Jul 2000 14:24:52 +0200 From: "Carsten Ziegeler" To: Subject: AW: Cocoon Configuration Thoughts Date: Thu, 6 Jul 2000 14:27:37 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 In-Reply-To: <3964761F.6670FF07@infoplanning.com> Importance: Normal Berin Loritsch wrote: > How about having your servlet engine restart Cocoon? Sure, this should work. > Anyways, what would > be the purpose of a dynamically reconfigured Cocoon? It is a > "cool" feature, > but once a site has been built and configured, it really shouldn't change. > What about having multiple instances in different Contexts? One for each > version of Cocoon you need. We have customers were the site MUST run 52x7x24. As the site is always extended and enhenced, there is the need for updating the configuration without stopping the site, even if this would be a short period. On the other hand we are planning to configure more than currently the cocoon.properties covers, e.g. some configuration for processors etc. And this information could change more often. ------------------------------------------------------------------------------------------ ...this mail was scanned for viruses by mailserver...