I'm a bit nervous for our rollout of a site with anticipated high volume
using C2.
I'm not sure the caching system will help us, at least not what I have
looked at so far.
Our pipeline is like this:
<map:match pattern="*/*/">
<map:generate type="serverpages" src="contentgen.xsp">
<map:parameter name="loc" value="{1}"/>
<map:parameter name="id" value="{2}"/>
</map:generate>
<map:act type="ex-get-stylesheet">
<map:parameter name="id" value="{2}"/>
<map:parameter name="location" value="{1}"/>
<map:transform src="stylesheets/{stylesheet}"/>
</map:act>
<map:serialize type="html"/>
</map:match>
The xsp does ESQL-calls and gets the XML content from the database.
The "ex-get-stylesheet" action gets the corrects stylesheet for the
document, based on location or per-document settings (All this is
configurable from the CMS interface)
Is there any way we can cache this pipeline? I can think of three
options:
1. Do a test in the xsp to check if the database has been changed, and
then
somehow signal that to the caching system.
2. Check the return from the xsp to see if transformation is needed.
3. Use squid or similar. (But I would try to keep this within Cocoon if
possible)
regards,
Rune,
Trondheim,
Norway
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
