News-Feeds:
TYPO3 Frontend Rendering explained
For about 6 months I have been working with two colleagues for one day per month on analyzing the frontend rendering process of TYPO3. We started with this because we were looking for possible performance improvements, and understanding how everything works is the best step for a start.
Finally, here is the first public version of our analysis. It consists of a detailed flowchart and is followed by a table with explanations at the end of the document.
I'm planning to include this into "Inside TYPO3" soon but look forward to your feedback and comments before that...
Kudos go to Regula Gantenbein and Andreas Kluser. Thanks a lot for the great work you did!
- michael
- Files:
TYPO3_Frontend_Rendering_Process_v1.5.pdf287 K
comments
September 22, 2007
14:56
I just wanted to say, that I really appreciate your work.
Thanks a lot!
--
cheers,
Steffen
September 24, 2007
18:55
Was looking for this for ages.
Thanks Monsieur Stucki.
September 24, 2007
18:59
Visuals can help so a lot and makes things understandable in minutes.
Very good, big +++
I hope this will be available in the docs so the info is not get loosed after some months.
September 25, 2007
10:37
Just one remark. The magnifying glass should appear in the legend as a pointer to another (sub) chart, too.
BTW: Which results came out of your analysis?
September 26, 2007
15:47
this helps alot with actual extension development.
September 27, 2007
10:52
I just wanted to ask if you also had a look at the FE-rendering process via TypoScript?
I was wondering why rendering a USER_INT object in a USER_INT function does not work.
If you (or anybody else) has an idea or the same problem, please contact me.
October 4, 2007
11:52
@Peter Luser:
A _INT object is placed in the cached content output as a XML-comment which is replaced at the end (see step 32 in Stucki's chart). Those are replaced only once and not recursively. So if your USER_INT generates other _INT comments, those won't be replaced anymore (I imagine that they are then simply outputted to your frontend).
Since your USER_INT will always be called non-cached, you can as well embed USER into it, as those also won't be cached (your USER_INT has to generate them any time). So it won't bring you any advantage to nest USER_INTs anyway.
Buzz is the official blog resource of the TYPO3 project. You can be part of Buzz too. If you want to blog about the achievements of your team or your personal involvement please check out our HELP section.
This documentation is great!
Thanks a lot!
--
cheers,
Steffen