[TYPO3-ect] tx_base - tslib_pibase modernized

[Franz Koch]

Hi guys,

>> Let's say this: Usually a cached object is a USER object and has
>> $this->pi_checkCHash set to TRUE, while for non-cached objects (USER_INT) it
>> is the opposite. I'm aware that it's currently possible to do this
>> differently, but practically I see no sense in it. For me it seems ok to
>> require that cached objects require cHashes all the time.
>>
>> So maybe we could just set $this->pi_checkCHash and $this->pi_USER_INT_obj
>> automatically, like this:
> 
> 
> I already have thought about this solution, but I fear it isn't that
> easy.
> 
> Imagine a typical search from (USER_INT) with a result browser
> (unlimited combinations of parameters). In the border there are a few
> little, nice static plugins (USER). In this case the USER plugins
> don't depend on parameters. (In fact they couldn't because we need a
> flexible URL for the result browser.)
> 
> In your suggestion each of this USER plugins would trigger checkCHash, if
> I understand it right. The USER plugins in the borders have themself no
> parameters to receive, but they would influence the USER_INT in the same
> way as if we would always activate checkCHash. Right? So we
> would run into the same problems with pageNotFoundOnCHashError = 1.

So it might be needed to modify the pageNotFoundOnCHashError processing for USER objects to be only triggered if a certain flag (maybe '$this->reactOnPiVars') is set or not? Or is $this->pi_USER_INT_obj exactly that flag?

Another idea would be to automatically switch a cached USER object reacting/listening to piVars to USER_INT if no cHash is given.

-- 
Kind regards,
Franz Koch