[TYPO3-dev] Cleaning up specific cached pages

[Steffen Kamper]

"Elmar Hinz" <elmar07 at googlemail.com> schrieb im Newsbeitrag 
news:mailman.1.1188254046.13488.typo3-dev at lists.netfielders.de...
> Steffen Kamper wrote:
>
>>>
>>
>> coming back to the cache-flags: There are two flags. When i look to my
>> cache-entries they are nearly never used, but the idea of the flags could
>> help a lot.
>> What do you think, if every extension by default use a cache-flag so it
>> would be easy to identify the cache-entries?
>>
>> vg  Steffen
>
>
> To use an up-to-date term you think of "tagging" the the cache entries?
> The controllers class name would be a good unique tag.
>
> Two easy functions would do the simple furnishment:
>
> tagMyCache($controllerClassName)
> flushMyCache($controllerClassName)
>
> The advanced furnishment could add a second parameter $someId to flush
> single entries:
>
> tagMyCache($controllerClassName, $someId)
> flushMyCache($controllerClassName, $someId)
>
> It would be up to the extension, how it would use the $id parameter.
>
> Elmar
>
>

Yes, exactly that way would be a good way to do.
$controllerClassName or in pi-Ext the prefixId are the best tags for easy 
identification.

As there is a second tag this could be used for beeing more specifiv, in 
piBase-world it could be pi1,pi2,pi3...,
in MVC it could be modulName.

Having this functions in lib or in core would make life much more easy (in 
my eyes).

It would also help to analyze if extensions doesn't have proper cache 
handling and flooding cachetable etc. I could imagine a BE-Module which 
shows statistic data for quick analyze.

vg  Steffen