Issue Feature Rejected

#30006Allow manual pruning of caching framework entries

Xavier Perseguers 09/19/11, 09:56 updated 10/11/11, 16:46

Description

In TYPO3 4.6, caching tables are automatically flushed when using the menu entry “Clear all caches”. At first glance, it makes sense but extension authors may have chosen to take advantage of the caching framework to build real-life application caches and expect the caching framework to let them handle pruning of outdated data.

Example for this is the egovapi extension which retrieves governmental information from a web service and caches them locally. Another web service endpoint returns list of recently updated data, effectively allowing the local cache to be actively flushed (typically by tags).

At the moment, the typical clear all caches call defects the clever caching that was implemented and worked in TYPO3 4.5 due to the lack of integrate cache pruning.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.