You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by Vadim Gritsenko <va...@reverycodes.com> on 2005/03/18 18:19:03 UTC

CForms DefaultCacheManager

Hi All,

Does anybody here remember why validities check in the DefaultCacheManager is 
done backwards, not as per SourceResolver contract? It first gets validity from 
the new source instead of checking validity of the old source.

I'd suggest reverting the check back, if it's Ok with everybody.

Vadim

Re: CForms DefaultCacheManager

Posted by Vadim Gritsenko <va...@reverycodes.com>.

Carsten Ziegeler wrote:
> Vadim Gritsenko wrote:
> 
>>Does anybody here remember why validities check in the DefaultCacheManager is 
>>done backwards, not as per SourceResolver contract? It first gets validity from 
>>the new source instead of checking validity of the old source.
>>
>>I'd suggest reverting the check back, if it's Ok with everybody.
> 
> +1

Done.

Vadim

Re: CForms DefaultCacheManager

Posted by Carsten Ziegeler <cz...@apache.org>.

Vadim Gritsenko wrote:
> Hi All,
> 
> Does anybody here remember why validities check in the DefaultCacheManager is 
> done backwards, not as per SourceResolver contract? It first gets validity from 
> the new source instead of checking validity of the old source.
> 
> I'd suggest reverting the check back, if it's Ok with everybody.
> 
> Vadim
> 
> 
+1

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/