Andrew Golightly wrote:

[ ... ]


I am not sure but i didn't found such a config file. I simply made a new action based on cocoon's HttpCacheAction and added that action to lenya's sitemap.xmap:

.....
.....
<map:match pattern="**">
   <map:act type="httpcacheaction"/>
   <map:act type="authorizer">
.....
.....

So I tried this by editing the sitemap.xmap for my publication:
<map:pipelines>
....

  <map:pipeline>
     <map:match pattern="**">
         <map:act type="httpcacheaction"/>
      </map:match>
  </map:pipeline>

...
</map:pipelines>

But I get an error coming back to me saying:
"Type 'httpcacheaction' is not defined for 'act' at"

Did you define the action in the sitemap like:

<map:actions>
   .....
   .....
<map:action name="httpcacheaction" src="org.apache.cocoon.acting.HttpCacheAction?">
     <minutes>15</minutes>
     <seconds>4</seconds>
   </map:action>
</map:actions>


I'm using lenya 1.4.

I then searched on the word 'cache' in this file, and the other elements I found were:

1)
<map:component-configurations>
     <global-variables>
       <cache-dir>work/cache</cache-dir>
     </global-variables>
   </map:component-configurations>
2)
 <map:select type="resource-exists">
             <!-- Read from cache -->
<!-- If configured within Apache then mod_lenya will nevertheless read from cache --> <map:when test="{global:cache-dir}/{../../1}/{../../2}.htmlDISABLED"> <map:read src="{global:cache-dir}/{../../1}/{../../2}.html" mime-type="text/html"/>
             </map:when>
             <!-- Write to cache and serialize -->
             <map:otherwise>

3)
  <!-- Write to cache for requests from live area -->
                   <map:select type="parameter">
<map:parameter name="parameter-selector-test" value="{../../1}"/>
                     <map:when test="live">



As far as i know this refers to the caching mechanism available in the default publication.

HTH
Jann



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to