[TYPO3-dev] Fight the no_cache parameter

[Elmar Hinz]

> 
> Instead, we should force USER_INT and extend it somehow to have special
> case - to cache it when neccessary:
> $cache_me = (is_there_search_query) ? FALSE : TRUE;
> 
> We need something that simple.

Yes we need something simple. Something that developers quickly understand
so that mistakes can be reduced.

Forcing USER_INT and caching inside will not work because USER_INT is
executed after the caching has happened.

Takin USER as default and making inner dynamic parts as USER_INT works.
That is what Joh has shown. That could be exended to your idea.

Regards

Elmar

-- 
Fight the no_cache parameter:
http://t3flyers.wordpress.com/2007/04/06/a-quick-guide-to-proper-caching-with-tslib_pibase-episode-1/
http://t3flyers.wordpress.com/2007/04/06/a-quick-guide-to-proper-caching-with-tslib_pibase-episode-2/