[TYPO3-dev] Is $this->pi_USER_INT_obj a conceptional mistake

[Elmar Hinz]

Hi,

I think the $this->pi_USER_INT_obj parameter has mainly disadvantages,
today. It confuses and hinders so many programmers to build extensions with
clean working links.

I propose to remove the no_cache parameter from the pi_linkTP() function
completely and the $this->pi_USER_INT_obj paramter, too.


Dmitry Dulepov wrote:
>> I think a general $this->pi_USER_INT_obj = 1 parameter is a conceptual
>> mistake  because not every link generated with the pi_-link functions
>> points back to the plugin.
> 
> It is just improperly named. Should be something like $this->pi_noCache.
> 

$this->pi_noCache would be wrong. Non caching is the effekt of the USER_INT
itself.

The main advantage is to suppress the no_cache parameter generated by the
pi_linkTP() function.  Without no_cache parameter pi_USER_INT_obj becomes
superflous.

(I don't understand why it suppresses the cHash parameter if the programmer
has decided to set $cache as pi_base link function parameter. That looks
like a real bug that has never been fixed.)

>> I propose to remove the no_cache parameter from the pi_linkTP() function
>> completely and to remove the $this->pi_USER_INT_obj setting with it.
> 
> Holy compatility cow dies... :)
> 

I wouldn't mourn for plugins that still depend on no_cache parameters. That
is a performance killer. It would force the people fix those corrupt
extensions.

I send a copy to the R&D team to ask for advice. This is also my question
for the T3DD.


Regards

Elmar