Jorg Heymans wrote:
Sandor Spruit wrote:
Folks,
I am trying to speed-up my app (a search engine) by using caching. The idea
is to to run a query once, and allow quick browsing through multiple
pages of results without redoing the query - which is an expensive processing
step. It does not seem to work as expected, in a way I do not understand! :-(
Caching with aggregated has come up numerous times [1], maybe one those
threads gives you a clue.
Otherwise, the logs are pretty good in finding out exactly which
component thinks it should not deliver cached content.
Also, try setting up your sitemap outside of flow and aggregate it with
a static file to isolate the problem ie
<map:match pattern="test">
<map:aggregate>
<map:part src="mytest.xml"/>
<map:part src="cocoon:/query"/>
</map:aggregate>
</map:match>
So far, it seems I have made two mistakes:
1/ I have misinterpreted the way the caching algorithm works
2/ Contrary to my assumptions: the Paginator Transformer is cacheable.
So it looks like I'll have to re-organize my sitemap just a bit, because
the Paginator
uses the page parameter when one's browsing and "invalidates" the cache.
Another
lession learned here today: handle your own assumptions with great care...
Sandor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
