[TYPO3-dev] Caching Framework

[Jigal van Hemert]

Bernhard Kraft wrote:
> Jigal van Hemert wrote:
>> As automaketemplate must always be compatible with all supported 
>> versions of TYPO3 there must (in the end) be a way to detect if the 
>> data should be (un)serialized or not. If there is such a mechanism I'm 
>> more than happy to incorporate that in automaketemplate.
> 
> The problem is that the serialize/unserialize is hardcoded into the 
> automaketemplate, the same way as it is into the core.
> 
> In my opinion, the core or automaketemplate code should never do any 
> serialize/unserialize for calling t3lib_BEfunc::storeHash or ::getHash 
> but instead let those methods take care if the data should get 
> serialized or not.

I agree. The situation for automaketemplate is however that it must support:
- ye olde caching methods
- the new caching framework which expects serializing
- (perhaps) the improved new caching framework which handles the storing 
completely by itself

So, if there is a way to detect the third version, I'll include support 
for that in automaketemplate (conditionally (un)serializing the data).

-- 
Jigal van Hemert.