[TYPO3-dev] stdWrap for all TLO's

[Steffen Kamper]

"JoH asenau" <info at cybercraft.de> schrieb im Newsbeitrag 
news:mailman.1.1204152060.21390.typo3-dev at lists.netfielders.de...

>
> ??? - What are the damages caused by a double stdWrap except some
> milliseconds of performance?
> And if there are such damages why does the possibility to use stdWrap
> recursively (yes, there is stdWrap.stdWrap.blah) exist?
> Even if the extension developer already applied stdWrap to his functions, 
> it
> doesn't hurt to have a default stdWrap anyway.
>
> What I'm asking for is just the option to add stdWrap parameters to any
> USER/USER_INT element regardless of what the developer of the plugin 
> already
> did.
> If there already is something available, fine, we don't have to use the
> default stdWrap then.
> But if there is nothing (which is the case for lots of extensions), the
> administrator can still use stdWrap parameters to process or wrap the 
> output
> of the plugin without having to use the COA workaround.
>
> To make sure the performance loss will only happen, if there really is a
> stdWrap parameter in the setup, there could be a check for the existance
> before the stdWrap function is called.
>

Hi Joey,

i think you're right, the only damage i see is wrong encapsualing with 
cached/uncached.
Double stdWrap only means double processing, but at different times. And 
normally these stdWrap-Operations are (conditional) wraps.

vg  Steffen