[TYPO3-dev] set_no_cache is bad. What's next?
Martin Kutschker
martin.kutschker-n0spam at no5pam-blackbox.net
Mon Apr 2 16:03:36 CEST 2007
Elmar HInz schrieb:
>>> 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").
>
> Wich shows this:
>
> 1.) It's more easy to reimplement such a function than to find it in the
> forest of docs or class API.
> 2.) It's not in the class you expect it.
I agree. Some of the Core functions are not where you expect them. I
think most of them are old internal functions made public. They are
therefor where they originally were used.
Masi
More information about the TYPO3-dev
mailing list