Christian,
When we've had the need to cache a query, we just throw the result (as a
DOM object) into the sesssion. I'm including the sample pipeline. I'll
typicailly aggregate the results of this with something else (usually a
dynamic query) and I'm all set. When I want to clear the cache, the
I just skimmed through the mailing list to find ideas of how to cache a
pipeline starting with a request generator and later on passing data
through the SQLTransformer.
Did you or anybody else follow up on this idea?
NB: Caching of the request generator would probably also need to cache
request
Subject: RE: caching proposals: SQLTransformer and Request
>
>
> > May be you should consider different design, which is suited
> > better for
> > the problem? XSP pages with ESQL provide easy ability to program any
> > caching behavior.
> >
>
> What?!? You just convin
> May be you should consider different design, which is suited
> better for
> the problem? XSP pages with ESQL provide easy ability to program any
> caching behavior.
>
What?!? You just convinced me to go from XSP/ESQL to SQLTransformer! The
problem with ESQL is the Java recompilation, which is
> From: Stephen Ng [mailto:[EMAIL PROTECTED]]
>
> A couple of things I'd like to do with Cocoon caching; let me know if
this
> is crazy.
>
> 1. Add caching to the request generator. Many of my pipelines are
> transformations based upon the request, and since requestGenerator
currently
> does no
A couple of things I'd like to do with Cocoon caching; let me know if this
is crazy.
1. Add caching to the request generator. Many of my pipelines are
transformations based upon the request, and since requestGenerator currently
does not support caching, it means those transformations are always
