[TYPO3-dev] set_no_cache is bad. What's next?

[John Angel]

>> (if the number of filter combinations is limited) {
>>
>>    you use a USER object and each combination is cached.
>>
>> } else {
>>
>>    you use a USER_INT, because an unlimited number of combinations should
>>    not be cached.
>>
>> }


It is workaround, not a real solution.

We need cache management from the extension, so the ext itself can simply
say "delete my cache" or "cache me".

E.g. for form submitting or article rating we need both combination: always 
cache, unless the form is submitted, when "delete only my cache" applies.