[TYPO3-ect] tx_base - tslib_pibase modernized

[Elmar Hinz]

>> 2.) $pi_checkCHash should be set to TRUE by default (I see it's not
>> implemented yet.) So in doubt caching works simply by selecting USER.
> 
> But won't this break a plugin specifically set to "USER_INT"? I think
> having caching on by default will frustrate a beginner who will "ask
> google" and find the solution of "set_no_cache()", where auto-magically
> everything "works", which is then kept in his extension.
> 

[...]

> My idea would be to have as little caching as possible (USER_INT by
> default) so that the beginner will see results without having to
> set_no_cache(). But then provide some "easy" ways to turn the script to
> a USER script. Or maybe have more information in the kickstarter near to
>  checkbox where the user chooses "USER" or "USER_INT"?
> 

One problem with $pi_checkCHash on by default is that to much caching
could be done. But the positive result would be a sytem that is easier to
understand.

If we break it down, what triggers caching?

1.) checkCHash has to be set on the receiving page
2.) a valid cHash in the incomming link

If $pi_checkCHash is on by default caching would be controlled
completely by the decision to create a valid cHash. That is what I would
call simplicity. The complexity would be reduced and more people would
understand the system.

Additionally there is the problem, that it is difficult to controll the
setting of checkCHash at all, as it can be triggert from any of the many
plugins inside a page, as far as I see. 

Elmar