[TYPO3-dev] t3lib_cache

[Daniel Bruessler]

Hello Steffen and Ernesto,

yes that caching-lib is a really good thing. Caching by pid is not 
enough, we all know it ;-)

What's about an additional cache-table for reg? So it's not only reg1 
and reg2, there can be more. When one of the table-attributes is a 
type-field then such a register can be integer or float or xs:ID or 
something.

It could be handled by ext_conf_template.txt, because the ext-author 
know best what CGI-var-combination should be cached - and so it can be 
changed by an admin easily.

But I've got no time to help coding it ;-(

Cheers!
Daniel


> Steffen Kamper wrote: on 17.01.2008 10:12:
>> Hi,
>>
>> cache is one of the most advanced things in TYPO3 and developers 
>> search for own methods to clear specific cache.
>> What do you think about creating a general cache API?
>>
>> My proposal is to bundle existing functions in one file, eg. 
>> t3lib_cache, maybe mostly static functions that can be called from 
>> extensions.
>> API should have functionality like
>> - creating chash from given piVars
>> - deleting cache of specific pid
>> - deleting cache from specific cHash
>> - register cache using fields reg1
>> - deleting cache with registered reg1
>>
>> What do you think? Please let me know you're ideas.
> 
> Sounds like a nice idea. The also include a wrapper for getHash and 
> storeHash from t3lib_pageSelect (or move them here and make the wrapper 
> in pageSelect), as these are probably not very known by people needing 
> their own caching.
> 
> Maybe at the same time we could enhance that "reg1" integer stuff with 
> some more advanced way of tagging cached pages for later pruning by 
> extensions. Currently it is only an integer, which really doesn't help 
> if every extension want to tag their "single views" using the uid of the 
> record that was rendered. An indexed varchar field would be much nicer.
> 
> Cheers,
> Ernesto