Jean-Baptiste Quenot wrote:
> * Carsten Ziegeler:
>
>
>>Imho as this is a bug, I think it doesn't make sense
>>to keep compatibility. I will update the status file
>>accordingly. Now if you want to have compatibility we could
>>keep the old implementation using a different class name
>>(DeprecatedCachingCoplet or something like that).
>
>
> As long as we can manage to find a code snippet to invalidate a
> CachingURICoplet, there is no need to maintain compatibility. We
> will update our application accordingly.
>
I just did the final fixes. So from now on you have to use temporary
attributes for caching, e.g. cid.removeTemporaryAttribute(CACHE) etc.
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
|