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

[Franz Holzinger]

Hello

Dmitry Dulepov a écrit :
> Franz Holzinger wrote:
>> But does this really work? When a USER object is cached, then normally
>> the plugin is not called any more. But how should the USER_INT part of a
>> USER object be changed then?
>> Maybe it has always to be one USER object called by a USER_INT object.
> 
> The idea is that you can convert USER to USER_INT *when* USER is executed at the first time. For example, if you have a TS property 
 > your plugin to make it non–cached, you could check that property and 
if it is set to "1", you just make USER_INT out of USER.
 > This will work because USER will be executed at that moment.

Yes, but if you have a part which changes after the USER has already 
been generated, then you cannot call the generation of the USER_INT 
again. Normally the page should be cached.

But Masi has written, that in TYPO3 there will be internally a marker 
for each USER_INT object. Then the PHP code for the USER_INT should be 
called each time again, even it is embedded in a PHP code by a cached 
USER object. The USER php code will not be called again, but the final 
output will still be generated dynamically, when the internal markers of 
all USER_INTs get replaced by their latest dynamic contents.


- Franz