[TYPO3-dev] set_no_cache is bad. What's next?

Martin Kutschker martin.kutschker-n0spam at no5pam-blackbox.net
Tue Apr 3 17:33:24 CEST 2007


R. van Twisk schrieb:
> Ernesto Baschny [cron IT] wrote:
>> John Angel wrote: on 02.04.2007 09:38:
>>
>>  
>>>> Or in other words to a caching on object/extension level instead on 
>>>> page
>>>> level.       
>>> Exactly, something like toi_cache ext approach.
>>>     
>>
>> The functionalty sounds exactly what we already have in core:
>>
>> t3lib_page::getHash()
>> t3lib_page::storeHash()
>>
>> which has always been available for plugins (table "cache_hash").
>>
>> What are the benefits of "toi_cache" over that generic caches?
>>
>> And following the thread of Masi, maybe we just need to enhance that
>> core methods a bit for more functionality?
>>
>> Cheers,
>> Ernesto
>>   
> Actually,
> 
> that is a bit to generic, Elmar made a a better example.
> But I would like to see a more intelligent way of caching data.

Interesting ideas.

Sounds like we should start with a Wiki page to define what use cases we 
want to support with our new cache API. After that we can create and 
implement it. The thread is interesting, but it's already very long and 
good ideas may be lost.

Masi





More information about the TYPO3-dev mailing list