TYPO3 Core

What about using the "pageCacheToExternalFiles" feature? It can be found in the Install Tool of 4.0.

This does not solve the problem. T3 is just writing every single bit in can write to the harddrive.. There has to be a 'do something when limit is reached' option.

For the example with the calendar it would probably better to use cHash, to only store days, that really exist in your database. So if a search-engine tries to spider 1970-01-01 - what might not be in your calendar - no correct cHash exists and nothing is cached.

But I like the idea of a global $TYPO3_CONF_VARS['SYS']['maxCacheSize'], that limits the cache size to a maximum. Not everyone has a own webserver, but a webhosting package with e.g. 100 MB of database space. Any browser, like firefox behaves similar for caching fetched web data - you can set a limit. But it has to be defined, what should happend if that maximum is reached:
a) Clear all cache
b) Clear the oldest cache data and behave like a "cache stack"

Possibly a better place for discussion on that issue is the dev-list on lists.netfielders.de?

Hi Oliver!
Well i don't think that the mailinglists and newsservers would be a good place to discuss this, as it would never reach the core of T3.. I have tried discussions in the list (with different topics) many times, but I almost don't get an answer there..

To your question about how T3 should react I'm going to give my standard answer.. ;) The admin should be able to decide somewhere.. Maybe in install tool?

It would be really great if something like this can be integrated into T3 4.1