Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 36012 invoked from network); 31 Jan 2000 22:41:57 -0000 Received: from unknown (HELO host-226.isettle.com) (216.123.48.226) by 63.211.145.10 with SMTP; 31 Jan 2000 22:41:57 -0000 Received: from cryptologic.com (localhost [127.0.0.1]) by host-226.isettle.com (8.9.3/8.9.3) with ESMTP id RAA11675 for ; Mon, 31 Jan 2000 17:47:08 -0500 Sender: rszeto@host-226.isettle.com Message-ID: <389610EB.9FFFA0EE@cryptologic.com> Date: Mon, 31 Jan 2000 17:47:07 -0500 From: Ricky Szeto X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: Cocoon Question... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hmm... maybe a better question to ask is this.. Are producers created once and used over and over again for all? or are they just throw-away objects that are disgarded after the execution of the request? What I originally assumed, was that the producers are kept and reused. That is why I wanted to have it get a properties list to know where to load up action handler classes(non-producers) that it can delegate operations to instead of doing them all by itself or having several producers doing these jobs. If producers where throw-away objects, then this design would be very undesireable, as a producer would be loading several action handlers for each request(while only using 1 of them) and then being discarded after the request is fulfilled. Any thoughts?