Kris Rasmussen wrote:
How does cocoon handle caching of xsp pages with esql tags? It seems
to me that cocoon would have to generate the xml output of the xsp
page every time the page is called, and thus would be unable to cache
any xsl translation latter? Is this true? If so would it not be a
I see - interesting idea. You are wanting to use requests to trigger
uncache events, similar to the asynchronous reload behavior of the sitemap
(or was that cocoon.xconf? or web.xml??).
But you are still doing that work for every request in your scheme, which
if you have a high load won't nece
I realize my approach is somewhat reversed, however, in pages that are accessed and change often it seems like it might be necessary to obtain acceptable performance. For example, if I had a poll on a home page that changes every second or so, it would be a huge waste to output the current value of
Cocoon does not automatically cache xsp pages with esql tags, but provides
a means for you to tell it to do so. Have a look at the caching xsp
sample, and probably the javadocs for the caching related classes.
In general, you'll need your generator (which is what your xsp produces
automaticall
On wto, kwi 01, 2003 at 12:43:29 -0800, Kris Rasmussen wrote:
>
> How does cocoon handle caching of xsp pages with esql tags? It seems to me that
> cocoon would have to generate the xml output of the xsp page every time the page is
> called, and thus would be unable to cache any xsl translation
How does cocoon handle caching of xsp pages with esql tags? It seems to me that cocoon would have to generate the xml output of the xsp page every time the page is called, and thus would be unable to cache any xsl translation latter? Is this true? If so would it not be a better idea to have the pag
