[TYPO3-dev] Caching framework: Usage inextensions

Björn Pedersen pedersen at frm2.tum.de
Wed Jun 1 08:37:47 CEST 2011


Am 30.05.2011 18:10, schrieb Christian Kuhn:
> Hey,
> 
> On 05/30/2011 04:36 PM, Jochen Rieger wrote:
>>> Your analysis is correct. This will only change in 4.6 with one of the
>>> pending cf patches.
>>
>> wouldn't this patch be something worth beeing done in 4.5 as well? Since
>> it is a long term support release...?
> 
> we're talking about https://review.typo3.org/#change,1722 here: And I
> think it needs a second patch to actually use the clearAll functionality
> (I'm currently unsure). I've planned to dig into this as soon as this
> one and the next 2 pending patches are in.
> 
> The problem with this patch is: It's huge. It is the next backport of
> flow3 changes to v4 and it already took me ~3 days to get it done
> (together with several pre-patches in v4 and flow3). At the moment I
> don't feel really comfortable to patch this big patch as-is to our
> stable version as well. We could however separate the 'clear also not
> instantiated caches' somehow, but that is not on my personal TOP1 list.
> 
> Regards
> Christian

I think the main problem is, how to get at the used caches if they are
not registered. The only way would be to iterate over
$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching'].

Björn





More information about the TYPO3-dev mailing list