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

[David Bruchmann]

----- Ursprüngliche Nachricht -----
Von:        Dmitry Dulepov <dmitry.dulepov at gmail.com>
Gesendet:   Freitag, 30. Oktober 2009 16:39:17
An:         typo3-dev at lists.typo3.org
CC:
Betreff:    Re: [TYPO3-dev] set_no_cache is bad. What's next?
> Hi!
> 
> Peter Russ wrote:
>> And if NOT cached -> no indexed search ;-)
> 
> Well, we talk about different things. May be I should say it differently: converting from USER to USER_INT is only possible if USER discovers that it always has to run as USER_INT. When can it happen? Some extensions (like ab_linklist if I remember correctly) has a setting named "no_cache" in their TS. They use set_no_cache. Instead they should convert themselves to USER_INTs.
> 
> Is this more clear? :)
> 

Hi Dmitry,

sure every hint brings a bit more light in the mystery ;-)
Many Extensions don't use the API as they should, so it's not 
astonishing that for caching it's applying too.
But those examples always are good to show a better way.

Thanks and best Regards
David