[TYPO3-mvc] Caching problem?

[Franz Koch]

Hey,

> If someone has problems with cache tables full of unnecessary cHashes, he or she probably uses some get parameters for the uncached action (with post data, it should be only one cHash which I think is necessary).

And that's exactly the issue why the feature request was raised. Just 
imagine a editAction which at least needs the uid of the record to edit 
in the GETvars will lead to yet another cache entry. If those cases 
wouldn't exist it would absolutely be ok to always have a cHash appended.

> For those cases it might be best to exclude the action arguments for uncached actions from the cHash. This is probably not easy to do generically, as same argument names might be used for cached and uncached actions. Can this be done via hook when the cHash is verified (check if action is uncached, if yes exclude it's arguments from verification)? The UriBuilder would have to support that, too, but I don't see that as a problem.

It is possible - I already manipulate GETparamters based on some Cookie 
values and revalidate the cHash - that's not a big deal, but at the 
point you have to do that we don't have all necessary information to 
detect uncacheable actions automatically (could be set in flexform etc. 
and TS-setup is also missing at this point).
If you do that on your own for your extension it's of course no problem, 
but I don't see a easy way to use some sort of autodetection at this 
point of the page rendering process.


-- 
kind regards,
Franz Koch