On Wed, 2002-04-10 at 17:32, Nick Airey wrote: > On Wed, 2002-04-10 at 16:31, Vadim Gritsenko wrote: > > > From: Nick Airey [mailto:[EMAIL PROTECTED]] > > > > > > > > So does anyone have any ideas why say AbstractAction isn't poolable? > >
Ok, for those interested in the answer, I'll summarize the answers I received on cocoon-dev: * the developer is responsible for defining the lifestyle of each action. * This is done by implementing either ThreadSafe (in which case there is only one instance used every time), or Poolable (in which case there are many instances, as defined by sitemap parameters for that action) * Not defining a lifestyle at all means that an instance will be created, used, and destroyed every time it is needed. This is probably not very efficient. Nick. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>