[TYPO3-dev] idea about shared cache_extensions db

Martin Kutschker masi-no at spam-typo3.org
Tue Sep 30 16:10:31 CEST 2008


Steffen Kamper schrieb:
> Hi,
> 
> Martin Kutschker schrieb:
>> Steffen Kamper schrieb:
>>> Dmitry Dulepov schrieb:
>>>> Hi!
>>>>
>>>> Jeff Segars wrote:
>>>>> There might also be some tie-in with the caching work that Dmitry,
>>>>> Ingo, and Olly did as part of Hacktontest.
>>>> Yes, this should be possible. Since we have many caching backends
>>>> available there, we can even store the information on the file system.
>>>> It does not have to be in the database really. It is not queried that
>>>> often. Once we have it in the new caching system, there could by an
>>>> extension with a CLI script to update the database from a cron job.
>>>>
>>>> What do you think?
>>>>
>>> +1 in general.
>>> I expierienced also with SQLite which is file based and the performance
>>> is not bad even with big files.
>>
>> Or a DB (like BerklyDB, not like RDBMS). A PHP-DB extension is probably
>> installed everywhere. I'm not so sure about SQLite.
>>
>> masi
> 
> since 5.2 SQLite should be compiled with most distributions.
> But if it's configurable it's no problem.

But why do we bother. Isn't the new Cache API (the one from FLOW3)
written so that you can change the backe end any time? So the high-level
code won't be bothered with the details.

Masi




More information about the TYPO3-dev mailing list