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

[Franz Holzinger]

Hello Joey,

JoH asenau a écrit :
>> But normally the biggest part is never changed and could be a USER
>> object. This is e.g. the single view of a product. Then there is only
>> a small dynamic part which changes frequently and cannot be cached:
>> e.g. the current amount of items in the basket for this FE user.
>> If I switch the whole output into a USER_INT, then nothing would be
>> cached at all. So a USER_INT could be a drawback in the case of a big
>> HTML part which will never change. A USER_INT is always much slower
>> than a USER object.
> 
> Switching with conditions is no good idea for huge plugins but just for
> login forms and the like.
> 
> But this one might help you with tt_products:
> http://www.sk-typo3.de/COA_INT-in-Extensions.190.0.html
> 
> Read this, and maybe use it at last, since this is the one we have been
> talking about once upon a time in Cologne - remember?
Yes, I remember our meeting and your explanations about using the 
TypoScript with many COA and COA_INTs. However I did not catch how to 
write the necessary php code to implement this. I have tried something 
with tt_board, but IMHO my written code for handling those many COA and 
COA_INT objects, one for each flexform view (code field), is not good.

> The magic lies in the combination of XXX_INT objects and functions.
> You can break down the caching to the smallest necessary element of a page
> this way and it is tested and works!
> 
> So use the source, Luke ;-)
The plugin tt_products has so many codes. I do not want to have a 
separate COA and COA_INT setup and main functions for each code. I want 
to use the USER or USER_INT for the plugin, but then only the dynamic 
parts should get their own COA_INT object. This is for the view of the 
amount of items in the basket and a control for the plugin, e.g. to 
count how often a product has been viewed in the single view.

I do not know, if also a mostly user dependant extension like 
sr_feuser_register should be built from COA and COA_INT objects. It 
could use JavaScript and Ajax to fill in the entry fields, then it could 
have a COA object in the cache. But if I use markers for the input field 
values, then it could not become a COA at all.

- Franz