[TYPO3-v4] What is happening with id 0?

[Steffen Kamper]

Hi Helmut,

Helmut Hummel schrieb:
> Hi Steffen,
> 
> On 09.09.10 22:00, Steffen Kamper wrote:
>> i figured it out
>>
>> $TYPO3_CONF_VARS['SYS']['caching']['cacheConfigurations']['cache_pages'] 
>> = array(
>>    'frontend' => 't3lib_cache_frontend_StringFrontend',
>>    'backend' => 't3lib_cache_backend_DbBackend',
>>    'options' => array(
>>      'cacheTable' => 'cachingframework_cache_pages',
>>      'tagsTable' => 'cachingframework_cache_pages_tags',
>>      'compression' => TRUE,
>>    ),
>> );
> 
> So that's the configuration you used for your site?
>

local dev and test site

>> the 'frontend' => 't3lib_cache_frontend_StringFrontend' doesn't work, is 
>> defect or unusable
> 
> Uhm, no. The StringFrontend is made for storing strings, not variables,
> thus no arrays can be stored.
> 
> But TYPO3 stores the cached data as an array:
> 
> if (TYPO3_UseCachingFramework) {
> 	$cacheData = array(
> ...
> $this->pageCache->set(
> 	$this->newHash,
> 	$cacheData,
> ...
> 
> So yes, you cannot use the StringFrontend for the "standard" TYPO3
> caches, but besides that it works perfectly for other cases. :)
> 

yes, it makes sense. Anyway it's a "valid" configuration, and if it's 
not usable i would expect an exception "StringCache cannot be used for 
storing arrays. Please change your frontend setting." (Ingmar, if you 
have a good wording, please quote it)

btw - i got this setting from Christian to test compressed cache, so i 
expected this is a valid config.

Just a sidenote: i also would expect that the cache is little more 
intelligent. If data !== string, then serialize it, that's what i would do.

vg Steffen