Cocoon Man wrote:
Actually, what is not clear for me is the relation there is between
the fact that an XSP is a Poolable component (which means there is a
pool of XSPs stored somewhere by Cocoon) and the fact that XSP are
stored by Transient-store.
I don't understand why I have to set some *pool-max* parameter for the
<map:generator name="serverpages"> component and some *maxobjects* for
the transient-store which handles previously loaded generators.
The ServerPagesGenerator needs to be pooled so that multiple requests
can simultaneously use it to generate XSPs (or to even locate them in
the store). If your system allows 10 concurrent users running the same
request then you would want 10 ServerPagesGenerators in the pool. This
keeps you from creating and destroying them on every request, which is
fairly expensive because each one has to be configured from the XML and
then setup various companion components.
The store is used the cache the output of the generator, so subsequent
requests with the same input, and which would get the same output, can
simply be served by returning the cached result.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
