David Duddleston wrote: > > > So in many ways the use case it alsmost identical (except Cocoon has 3 > > stages where you only have 2). > > In the grand scope, there will be several stages (at least 7 in some cases) > a newly retrieved URI will go through before the end results are achieved > which as an indexed document. I assume that the difference of having 7+ > stages vs. 2 or 3 is no big deal. > > > >I hope this makes sense... I have a feeling it does, sense I > > think this is > > >the kind of stuff Avalon was created for and you people are doing this > > >extact thing already. Am I on the right track here? > > > > It makes sense ;) You definetly want to have a look > > org.apache.avalon.excalibur.component.* which has a ComponentManager that > > already does the Pooling et al. > > Cool, I will check it out. > > > I think Berins whitepaper actually > > describes it in more detail and how it is used in Cocoon2. > > Where might this be. I looked around the Cocoon2 and Avalon projects, but > did not find it. > > Thanks
It's still being developed, and will be made available as soon as is possible. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
