[TYPO3-dev]  set_no_cache is bad. What's next?
    Dmitry Dulepov 
    9f4eetb02 at sneakemail.com
       
    Thu Mar 29 15:04:02 CEST 2007
    
    
  
Hi!
 From time to time I see that people try to use $TSFE->set_no_cache() in 
extensions. You know what happens next: no caching for pages, 
performance is terrible, web server is not responding, etc. At the same 
time, sometimes, in really rare cases caching must be disabled. But 
definitely not this way from extensions.
Should we change this function in some way? Should it explain people 
that using it is no-good?
Personally I would vote for radical methods like (1) keeping it but 
emptying or (2) writing commented phrase inside generated FE page that 
set_no_cache was used, so do not expect good performance.
Any other ideas/opinions?
-- 
Dmitry Dulepov
Web: http://typo3bloke.net/
Skype: callto:liels_bugs
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
    
    
More information about the TYPO3-dev
mailing list