[TYPO3-mvc] cache handling and handling of 'no_cache' parameter

[Franz Koch]

Hi Sebastian,

>> 2) use of the 'no_cache' parameter for actions that are not allowed to
>> be cached (create,edit,etc).
> Actually it should *not* use the no_cache parameter for such actions.
>
>> Although this is probably the easiest way to achieve this, it's not the
>> best to do. A dynamic switch of the plugin(s) to USER_INT might be a
>> good/better idea in this case.
...
> This is what is done. We switch to user_int via TypoScript if that
> action is supposed to be un-cached (that's why we need a list of
> uncached actions on plugin registration).
>
> So, if you investigate the generated TS, you'll find that as well...
> Somehow it seems it does not work for you?

I have to confess that in my half asleep condition yesterday (which btw. 
still applies this morning) I only did some global search all over 
extbase for the term "cache" and noticed quite some "no_cache" stuff. So 
I assumed it's done with no_cache. If not - perfecto. But I'll check 
that again.

You and all extbase/FLOW3 guys are definitely my heroes. It's a lot of 
fun working with extbase/fluid once you know how to deal with them.

-- 
kind regards,
Franz Koch