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

[David Bruchmann]

----- Ursprüngliche Nachricht -----
Von:        Martin Kutschker <masi-no at spam-typo3.org>
Gesendet:   Freitag, 30. Oktober 2009 11:10:17
An:         typo3-dev at lists.typo3.org
CC:
Betreff:    Re: [TYPO3-dev] set_no_cache is bad. What's next?
> David Bruchmann schrieb:
>> 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?
> 
> TYPO3 caches pages *, not plugins.
> 
> Masi
> 
> * there are two cases:
> 
> a) a complete static page without dynamic parts
> b) a page with dynamic parts (USER_INT, COA_INT and others)
> 
> For case b) TYPO3 will cache an HTML page with special HTML comments. When the page is delivered to
> the client the comments are replaced with whatever the dynamic objects return.
> 
> Any further caching must be done by custom code.

Hi Masi,

thanks for that description, that helps a bit.
I think I have to read a lot of code to understand everything concerning 
cache.
In the moment it's still not so clear because there are a lot of 
different caching-tables.

Thanks and best Regards
David