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

[JoH asenau]

>> IMHO this is how most of the extensions should be working and this
>> is how tt_products, tt_news and the like could be tuned to work much
>> faster than they currently do.
>
> Yes, this seems to be a good solution for the single view. But how
> should this work for the list view of products, where you also have a
> category header and sorting of products? All products of a category
> are listed together in their own block. You have a basket part as
> USER_INT for each product on the list view.

Yes - and where is the problem?
Although I have to admit that it might be faster to render the whole list as
a USER_INT in this case.
But anyway it will be better than using set_no_cache()

So again - where is the problem?

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com