[TYPO3-dev] set_no_cache is bad. What's next?

[David Bruchmann]

----- Ursprüngliche Nachricht -----
Von:        Steffen Kamper <info at sk-typo3.de>
Gesendet:   Freitag, 30. Oktober 2009 10:35:24
An:         typo3-dev at lists.typo3.org
CC:
Betreff:    Re: [TYPO3-dev] set_no_cache is bad. What's next?
> Hi,
> 
> David Bruchmann schrieb:
> 
>>
>> cHash and Cache always is a bit mysterial, so I take the chance to ask 
>> about a special case:
>>
>> I've one Extension with several plugins. The cHash is build for all 
>> together I think and the result isn't correct. How can I force that 
>> each plugin is cached separately and that content of several plugins 
>> isn't merged in one cHash?
>>
> 
> cHash is built with the getVars. If you use different plugins you should 
> have different prefix and as result different cHash. Look to cHash 
> generation t3lib_div::cHashParams.
> 
> There are also possibilities to tag cache for your plugin by using reg1 
> ($TSFE->page_cache_reg1)
> 
> vg Steffen

Hi Steffen,

thanks for your hint's.
I'll take a look in the source and will test it.

In the Contentelements I save and load userdefined Flexforms (so the 
Contentelements can consist of different Flexforms).
Sure, the URL-Params point to the cached Content, (nearly) regardless of 
kind but in the moment I'm not quite sure if I'll get it.
Problem is that I've to clear the whole cache after updating the kind of 
flexform in one Content Element.
But thinking now about the mechanism only the cache of that element has 
to be refreshed - here I miss usability for the customer, perhaps I've 
to integrate something in the BE-Module?
Normally changed Elements should be refreshed automatically - that's 
what I read, not only what I expect but it doesn't work always in my case.

Thanks and best Regards
David