[TYPO3-dev] Resultlist & Details View USER_(INT)

[Martin Kutschker]

JoH schrieb:
> 
> Since when does a USER object disable caching for the complete page?

Every USER that has some dynamic output like "list view" calls 
$GLOBALS["TSFE"]->set_no_cache().

USER_CINT solves this problem.

It works as follows:

When TYPO3 encounters a USER_CINT object during page generation it calls 
the plugins function (like it happens with a USER). The function decides 
then, if it wants the plugin output content to be cached. If so it 
returns the content as string (as usual). But if it thinks that the 
piVars call (or SOME OTHER PLUGIN CONFIGURATION - it realy is up to the 
developer) for a dynamic content it returns FALSE. When the plugin 
returns FALSE, TYPO3 will store the plugin for later retrieval for later 
(like it happens with a USER_INT).

When TYPO3 comes to the final part of page delivery when USER_INTs are 
executed now it is also time for USER_CINTs. They are called again with 
a flag that tells them there are in the "USER_INT"-mode. So they now how 
to react.

Masi