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 35662 invoked from network); 21 Feb 2001 14:13:54 -0000 Received: from fw.infoplanning.net (HELO infoplanning.com) (@209.8.58.131) by h31.sny.collab.net with SMTP; 21 Feb 2001 14:13:54 -0000 Received: (qmail 8704 invoked from network); 21 Feb 2001 14:16:14 -0000 Received: from unknown (HELO apache.org) (192.168.0.189) by inet with SMTP; 21 Feb 2001 14:16:14 -0000 Message-ID: <3A93CC62.3078638@apache.org> Date: Wed, 21 Feb 2001 09:10:42 -0500 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: AW: [C2]: Component Pooling and recycling References: <3A93C720.D31AA41C@apache.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Berin Loritsch wrote: > > That was my thinking when I created the PoolClient interface. I would > really like the ComponentManager/Selector interfaces to remain "pure". > Especially since that is the way they are cast in the whole of Cocoon. > Your proposed solution will cause us to be required to cast as > CocoonComponentSelector--which is not a guarantee. We should lobby > Avalon for the change to the official interface--and use PoolClient > in the mean time. I have requested the interface change in the Avalon-dev list, we will discuss it, and hopefully it will be Ok'd quickly.