Hello Robert,

I asked around a little bit here, and there are others thinking it should be 
quite possible to use shared (open source) caches. Only thing that you have to 
build it yourself in cocoon because at the moment it is not in there yet.

What really may interest you though is the following: In the current cocoon 
distribution (2.1.8 and earlier) , the EHDefaultStore.java did NOT enable 
parameters to set "timeToLiveSeconds" and "timeToIdleSeconds". For the coming 
release of cocoon 2.1.9 (withing 2 weeks?) you can define these two parameters 
(or just one of them) in your cocoon.xconf: For now, default EHCache 
configuration is that everything is cached eternally! This means, once cached, 
it will stay there forever.

In the next release, EHDefaultStore.java will be replaced by 
http://svn.apache.org/viewcvs.cgi/cocoon/trunk/src/java/org/apache/cocoon/components/store/impl/EHDefaultStore.java?rev=332608&view=markup

You can now for example configure your store like:

  <store logger="core.store">
    <parameter name="maxobjects" value="1100"/>
    <parameter name="eternal" value="false"/>
    <!-- 1 day -->
    <parameter name="timeToLiveSeconds" value="86400"/>
    <!-- 3 hours -->
    <parameter name="timeToIdleSeconds" value="10800"/>
  </store>

meaning, that no matter what, the cached document will ALWAYS be removed after 
one day, AND it will be removed after 3 hours of no request for it. 

In your case, for example, you could try to set timeToLiveSeconds to 0, meaning 
it is not taken into account, and your timeToIdleSeconds to for example 1 day. 
Documents not fetched for longer than one day will now be removed from your 
cache. 

Hope this is interesting for you,

Regards AS


> Hi Ard,
> 
>  From your mail I assume you see little chance that they 
> could share the 
> same cache. I suspected so...
> 
> >Apart from your question which is quite interesting, and I 
> would certainly not know haw different cocoon instances could 
> be able to have knowledge about validities and cachekeys the 
> other cocoon instance created, I am very interested how you 
> and up with a 30 GB (cocoon) cache!! That is quite amazing! 
> Is it a lot of binary data? You could better cache this once 
> in apache, or perhaps in the load-balancer..not within 
> cocoon. Anyway, what is the 30 GB ?
> >
> >  
> >
> Well, I am actually serving quite a lot of information over Cocoon:
> 
> iHOP is an online service that provides this gene guided network as a 
> natural way of accessing the more than 12 million abstracts in PubMed 
> and brings all the advantages of the internet to scientific 
> literature 
> research. The actual network provided in iHOP contains two million 
> sentences and 30000 different genes from human, mouse, Drosophila, C. 
> elegans, zebrafish, Arabidopsis, yeast and E. coli.
> http://www.ihop-net.org/UniPub/iHOP/
> 
> 
> Btw, I reduced the number of objects to be cached (today). I 
> am curious 
> if this will do it.
> 
> Thanks,
> 
> Robert
> 

-- 

Hippo
Oosteinde 11
1017WT Amsterdam
The Netherlands
Tel  +31 (0)20 5224466
-------------------------------------------------------------
[EMAIL PROTECTED] / http://www.hippo.nl
-------------------------------------------------------------- 

> 
> >  
> >
> >>Many thanks for any help,
> >>
> >>Robert
> >>
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>    
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >  
> >
> 
> -- 
> --
> Have you tried iHOP yet? http://www.ihop-net.org/UniPub/iHOP/
> 
> --
> Robert Hoffmann, PhD
> 
> Memorial Sloan-Kettering Cancer Center, MSKCC
> Computational Biology Center, cBIO
> Chris Sander's Lab
> 
> 1275 York Avenue. New York, NY 10021
> phone +1 646-735-8081, fax +1 646-735-0021
> [EMAIL PROTECTED], http://www.cbio.mskcc.org/~hoffmann/
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

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

Reply via email to