cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <gkossakow...@apache.org>
Subject Re: Moving reduced version of CachingSource to core | Configuration issues
Date Mon, 26 Mar 2007 18:36:57 GMT
Reinhard Poetz napisaƂ(a):
> Vadim Gritsenko wrote:
>> Reinhard Poetz wrote:
>>
>> Actually it already should be working this way? See CachingSource line 
>> 427.
> 
> I guess with some additional configuration it should be possible to get 
> this stuff working but ...
> TBH, I only want to have a url like 
> caching:http://www.example.org/rss.xml?cocoon:cache-expires=600 without 
> any further configuration. The content should be available whatever 
> happens to the RSS feed and should even survive restarts of Cocoon by 
> default. After 10 minutes it should be tried to update it but shouldn't 
> throw away the previous content in the case that the refresh runs into 
> an exception.
> 
> This brings me to another point: What is the best option for the retry 
> strategy? There could be some smart default value (e.g. 10 % of the 
> cache-expires value ... don't know whether this is really smart ;-) ) 
> that could be overrided by a cocoon:cache-retry parameter. WDYT?

Whatever way you choose to achieve this I'm +1 for refactoring, removing 
unnecessary dependencies and adding fall back mechanism.

-- 
Grzegorz Kossakowski


Mime
View raw message