[TYPO3-dev] Typoscript menu rendering and its caching

[Frank Gerards]

Hi,

yeah we got an CUR/ACT state in it ofc, didnt think oft that ;).

Thx for your help

Greetings,

frank

-----Ursprüngliche Nachricht-----
Von: typo3-dev-bounces at lists.typo3.org [mailto:typo3-dev-bounces at lists.typo3.org] Im Auftrag von Bernd Wilke
Gesendet: Mittwoch, 7. Dezember 2011 13:23
An: typo3-dev at lists.typo3.org
Betreff: Re: [TYPO3-dev] Typoscript menu rendering and its caching

On Wed, 07 Dec 2011 12:58:28 +0100, Frank Gerards wrote:

> Can somebody explain to me why the menu is rendered from scratch on
> every uncached page I hit

first thing which comes to mind:
on each page the ACTual and CURrent menu-entries are different.

if you do not render these (and similar) states the menu could be cached, 
but how to tell the difference? 
 
> and what is the default behavior to be expected ?

like it is?

for performance optimizing:
inspect the PHP-code. look for hooks.
optimize the code. 
for core-optimization make a entry on forge and provide patches.
optimize your own code:
e.g. cache your userfunc-results where possible.

bernd
-- 
http://www.pi-phi.de/cheatsheet.html
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev