[TYPO3-ect] suggested way of mixing up USER and USER_INT in one plugin-instance

[Steffen Kamper]

"Elmar Hinz" <elmar07 at googlemail.com> schrieb im Newsbeitrag 
news:mailman.1.1199021313.31075.typo3-team-extension-coordination at lists.netfielders.de...
>>
>> Hi,
>>
>> what MASI is talking about is the solution Joey gave a while ago. I don't
>> have his original link, but i have written a german tut of this at [1]
>>
>> It is easy to implement this by generating the TS dynamicly
>>
>> public function getUSER_INTobject($function) {
>>  $TS['conf']='COA_INT';
>>  $TS['conf.']['10']='USER';
>>  $TS['conf.']['10.']['userFunc']=$function;
>>  return $this->cObj->cObjGetSingle($TS['conf'],$TS['conf.']);
>> }
>>
>> vg  Steffen
>>
>> [1]  http://www.sk-typo3.de/COA_INT-in-Extensions.190.0.html
>
> Hi Steffen,
>
> thanks for the nice tutorial. I will think about how it can help for
> lib/div.
>
> But there are still questions?
>
> 1.) In JoHs examples the outer object is the COA and the inner object the
> _INT. Is your example right?
>
> 2.) Assuming it is called in an extension that is itself USER (the outer),
> why dont you write:
>
> public function getUSER_INTobject($function) {
> $TS['conf']='USER_INT';
> $TS['conf.']['userFunc']=$function;
> return $this->cObj->cObjGetSingle($TS['conf'],$TS['conf.']);
> }
>
> public function getUSERobject($function) {
> $TS['conf']='USER';
> $TS['conf.']['userFunc']=$function;
> return $this->cObj->cObjGetSingle($TS['conf'],$TS['conf.']);
> }
>
> What is the purpose in the nested way you suggest?
>
> Regards
>
> Elmar
>

Hi Elmar,

in Joeys example outer object is COA to demonstrate different use cases and 
to show, that the inner COA will show the cached result, but inner COA_INT 
shows uncached result.

You are right, that there is no capsulating with COA needed if you use USER 
or USER_INT. COA was used for more Objects.
So you can use it the way above with USER and USER_INT.

vg  Steffen