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 61789 invoked from network); 23 Jul 2000 16:44:45 -0000 Received: from stargazer.dataway.ch (HELO dataway.ch) (qmailr@195.216.64.144) by locus.apache.org with SMTP; 23 Jul 2000 16:44:45 -0000 Received: (qmail 4845 invoked by uid 0); 23 Jul 2000 16:44:42 -0000 Received: from zh2-4.dial.dataway.ch (HELO pwr.ch) (root@195.216.80.132) by stargazer.dataway.ch with SMTP; 23 Jul 2000 16:44:42 -0000 Received: (qmail 3341 invoked from network); 23 Jul 2000 16:39:11 -0000 Received: from donald.pwr.ch (HELO pwr.ch) (giacomo@10.20.30.103) by simba.pwr.ch with SMTP; 23 Jul 2000 16:39:11 -0000 Sender: giacomo Message-ID: <397B1FAE.E2CB1CD1@pwr.ch> Date: Sun, 23 Jul 2000 18:39:10 +0200 From: Giacomo Pati Organization: PWR Organisation & Entwicklung X-Mailer: Mozilla 4.72 [de] (X11; U; Linux 2.2.14 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Cocoon dev Subject: C2 thread savety Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I've encountered a problem concerning thread savetyness. The old C2 sitemap engine instantiated a component object (generator, serializer, etc.) for every request. The new sitemap engine does not. Now we should decide if a sitemap component should be thread save, or not or if we could have a mixture of both (indicated in the sitemap as an attribute like thread-save="yes"). Giacomo -- PWR GmbH, Organisation & Entwicklung Tel: +41 (0)1 856 2202 Giacomo Pati, CTO/CEO Fax: +41 (0)1 856 2201 Hintereichenstrasse 7 Mailto:Giacomo.Pati@pwr.ch CH-8166 Niederweningen Web: http://www.pwr.ch