Return-Path: <bloritsch@apache.org>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 85013 invoked from network); 22 Feb 2001 15:07:42 -0000
Received: from fw.infoplanning.net (HELO infoplanning.com) (@209.8.58.131)
  by h31.sny.collab.net with SMTP; 22 Feb 2001 15:07:42 -0000
Received: (qmail 21978 invoked from network); 22 Feb 2001 15:10:13 -0000
Received: from unknown (HELO apache.org) (192.168.0.189)
  by inet with SMTP; 22 Feb 2001 15:10:13 -0000
Message-ID: <3A952A7F.3411D9D7@apache.org>
Date: Thu, 22 Feb 2001 10:04:31 -0500
From: Berin Loritsch <bloritsch@apache.org>
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: <NEBBLPMLKKCJBKEOKNFHIEIMDLAA.cziegeler@sundn.de>
 <3A93D6D2.E0AD7DDA@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:
> 
> Carsten Ziegeler wrote:
> >
> > > Berin Loritsch [mailto:bloritsch@apache.org] wrote:
> > >
> > > > What about the Recyclable components? Is it correct, that a Recyclable
> > > > component can be used without Poolable (or PoolClient) ? If so, who is
> > > > responsible for calling recycle() ?
> > >
> > > The ComponentPool is responsible for calling recycle().  However, since
> > > you already have a reference to the Component, you can reuse it as long
> > > as you call recycle() between each use.
> > >
> > Then I would suggest do add a test for Recyclable in the ResourcePipeline
> > to recycle a component which is not PoolClient.

Ok, Carsten, you can go to town now.  Every time a Component is Selected or
LookedUp, we need to Release them.  I made the initial changes with the new
ComponentManager/ComponentSelector changes, but I didn't go so far as to
remove PoolClient....