[TYPO3-dev] why USER "_INT" ?

[Jigal van Hemert]

Stefano Cecere wrote:
> i know, stupid question, but does anybody know why a non cached object 
> is called USER_INT ?
> what does this "_INT" mean?
> 
> i ask because i have some difficulties to memorize it (i often don't 
> remember which of USER or USER_INT is the cached one :)

The explanation won't help you to memorize it :-)

In TSRef you can see in the description of PHP_SCRIPT, PHP_SCRIPT_INT 
and PHP_SCRIPT_EXT the origin of the _INT suffix.

So the suffix comes from the difference between _INT and _EXT, but the 
suffix is used for COA and USER because the _INT versions of these are 
handled the same way as PHP_SCRIPT_INT: only a marker ("divider-string") 
is inserted in the cached page content and this marker is replaced by 
the content generated by the USER_INT or COA_INT object after the page 
is fetched from the cache.

This behaviour caused the suffix _INT to be used for COA_INT and 
USER_INT, although it might not be that obvious for most people.

Regards, Jigal.