[TYPO3-dev] Announcing TYPO3 4.2 Beta 3

[JoH asenau]

>> An option was introduced to completely turn off the no_cache
>> parameter, although this option is off by default it is likely that
>> is will get enabled by default with TYPO3 4.4 or 4.5, please make
>> sure you use proper caching in your extensions. A new input field
>> type is available
>
> I think disabling no_cache is a very bad idea. Instead set_no_cache()
> should be disabled from extensions. The  way to do it is simple: save
> and restore value of no_cache var in a local var of
> tslib_cObj::USER() function. That's all. Sometimes no_cache makes
> real sense and disabling it completely is a bad thing.
>
> I am not sure who had the idea to disable no_cache. I do not remember
> seeing it in core list. But I doubt we can set it by default to
> "disable". This is bad idea. Machine must not try to be more clever
> than human.

Read it again and pay attention to the double negation ;-)

An _option_ was introduced to completely _turn off_ the no_cache parameter,
although this _option is off by default_

So you _can_ disable no_cache but by default it is still on.

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
openBC/Xing: http://www.cybercraft.de
T3 cookbook: http://www.typo3experts.com
Jobs: http://www.professionals-only.com