[TYPO3-dev] cObj Cache, COA and HMENU

[JoH asenau]

> If I am right, I would file a request to improve TsRef. It was by mere
> chance,
> that I stumbled upon the entry in forge.

Please don't do that, since this would lead to the scenario we already 
got with IRRE and workspaces. People might not accept an upcoming fix 
due to the behaviour already being documented somewhere. ;-)

IMHO this is a bug that should be fixed or at least a missing feature, 
if the responsible CMS team members don't accept it as a bug.

There must be a check around cObjGetSingle for any kind of nested 
cObject COA, COA_INT, HMENU etc. to properly provide the return of 
cached content in case there is
a) a cache setting within the stdWrap methods of this object
b) an available cache entry for the matching key

This will give us a huge performance boost, since the current approach 
will render each and every nested COA even though there might be a 
cached entry that will be returned later anyway.

Instead of having to rewrite every nested cObject the way as described 
in the TEXT example, we could just use the cache as one would expect it 
to be used by definition.

Just my 2 cents

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com