cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Howard <>
Subject Re: database caching
Date Wed, 02 Apr 2003 20:21:24 GMT
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 necessarily give better performance.

Why not do a time-based cache that expires every second or minute, etc.?

I had been wanting to allow for asynchronous cache behavior and will look 
into it, but for now if you really want to go that way you'll either need 
to do it that way yourself, or write a custom transformer to do that as you 
proposed.  I tend to dislike transformers with side effects in that sort of 
scenario, but it should work.


At 01:54 PM 4/2/2003, you wrote:

>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 the poll (a single number) every time the page is accessed and 
>then regenerate the xml for the whole page and then transform it all 
>again. Rather, it seems that it would be much more efficient if the call 
>to the database was put off until the entire page was transformed and 
>cached first. I realize this is possible to do with cocoon with 
>transformers, however I was curious if there was any way to do it with 
>esql and xsp.
>Please correct me if I am wrong, or if this added complexity for high 
>traffic pages is not necessary.
>  Leszek Gawron <> wrote:
>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 latter? Is this true? If so would it not be a better idea to 
> have the page be translated into html before all database code is called 
> and then insert the database code at the very end and output as a jsp 
> page or something?
>Is that the way other server side frameworks do? Remember that the most
>important thing is data, which is being generated at the beginning and then
>the presentation is applied. Your approach is completely reversed.
>Take look at Velocity - maybe it could solve your problems
>| / \ | Leszek Gawron // \\
>\_\\ //_/ _\\()//_
>.'/()\'. Phone: +48(600)341118 / // \\ \
>\\ // recursive: adj; see recursive | \__/ |
>To unsubscribe, e-mail:
>For additional commands, e-mail: 
>Do you Yahoo!?
><*>Yahoo! Tax 
>Center - File online, calculators, forms, and more

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message