[TYPO3-core] RFC #9284: Feature: tt_content.starttime/endtime have now effect on caching (with patchfile now, sry)

[Michael Stucki]

Hi Dmitry,

> Michael Stucki wrote:
>> - Of course this requires modification to all plugins. The reasonable
>>   default should be a timeout of 1 day (just like now).
> 
> I did not understand this bit. Do you mean every plugin in every
> extension from TER? This is not realistic at all.

Yes. New extensions should set this value appropriately. Old (existing)
extensions should just have a fallback like now which is 1 day.

Because of this default value, they don't need to be modified for this
(of course!) So what exactly is not realistic with this plan?

>> - Additionally, some config options could then be removed (like
>>   config.cache_period and config.cache_clearAtMidnight)
> 
> They couldn't. These options are deadly useful and they are used by many
> projects. Do not break these things. Cache period can be set smaller now
> (like 3h) for some web sites, which require it.

I agree, this could be useful. However, it should not be needed anymore
since plugins know their own timeout much better...

> Same goes for clearing cache at midnight: this is necessary for certain
> crawler configurations (for example, if a plugin adds entries to the
> crawler manually). So removal of these options is not an option at all.

I've never seen any practical use in this configuration as the default
value for config.cache_timeout is only 24h already. However, I'm open to
learn for what it could be used. And naturally, we can keep the property
until then... ;-)

- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/