[TYPO3-mvc] Caching problem?

[Xavier Perseguers]

Hey Franz,

>>> The mentioned snippet in the UriBuilder got implemented after a feature
>>> request to remove the cHash on nonCached uris, which is correct behavior
>>> and should be kept. If we'd always append the cHash, the very same page
>>> would be added several times to the page cache although it's content is
>>> set to USER_INT and isn't even part of the cached page. So this is also
>>> a no-go.
>>
>> I agree but current behavior is a no-go too and *must* be fixed with the
>> next release of 4.5 as it isn't reliable.
>
> Configuring piBase extensions like this will give you the same result ;)

I know but as the same time we all know so many extensions where the 
plugin was set to USER_INT or the whole cache was invalidated because 
the developer did not understand the whole caching stuff and how to deal 
with it correctly.

> I agree that this has to be fixed ASAP - but it's not that much of a
> no-go then always appending a cHash for me.

Well, with Extbase, the meaning of "actions" is really clear, much more 
than with pibase when someone did not have a clear separation of methods 
(which happened quite often to be honest). Having an official MVC 
framework forces the extension to be automatically at least "a bit 
cleaner". Having an index action (often listing some records) being 
cached is really common and wanted because generating it again and again 
because of some other action need is not "logical". Furthermore, perhaps 
your index action only provides additional edit action links if you are 
logged in...

I agree that having cHash for uncached actions is a bit weird at first 
but it definitively makes sense to let the USER somehow become a 
USER_INT once it has been cached.

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org