[Typo3-dev] Empty cHash problem

[Elmar Hinz]

> 
>>Either this is not precise enough or tells something else then the
>>article. There isn't a problem when the cache is already filled in the
>>article. The problem is filling the empty cache with the right stuff.
> 
> 
> If the cache is empty, it will be filled by the first attempt to request
> the given page. The problem is if we fill the cache, but the content is
> not really meant to be cached for that combination of parameters. In the
> article, this results in:
> 

There we met. That's what I said.

> checked (if present, TYPO3 will check it on its own, if not present or
> empty, TYPO3 needs the plugins to inform if a checking is needed, which
> is what this section of the article is about).
> 
> 

It is informed by setting the useCacheHash paramter in the plugin. Still 
  I don't make friendship with this concept. Programmers could forget to 
set it. Why can't it be done automatically for USER-objects?

First checking if there are more parameters then type and id. And if so 
requireing a valid cHash before any saving action takes part, to say it 
shortend.

I know there could be some other parameters around like the L-Parameter 
for languages. But that information could be fetched from TypoScript Setup.

> 
> 
>>That is exactly my thesis. The effect would be the same. Even if there
>>isn't an empty cHash but an invalid one.
> 
> 
> Right, just that with invalid ones the plugin writer won't even be
> bothered with it, which is not the case if there is no, or an empty
> cHash value.
> 

And why? Because if a wrong cHash is discoverd, caching is disabled at 
all. That point I missed. I imagined parametes would be thrown away, so 
that it would behave like no parameters at all.

Best regards

Elmar




-- 
Climate change 2005: New Orleans, Sahel, Bangladesh, Spain, Portugal, 
Austria, Swiss, France, ...
Production of CO2 is killing people.
Production of CO2 just for fun is killing people just for fun.