[TYPO3-ect] The Big Plan

[Ernesto Baschny [cron IT]]

R. van Twisk schrieb am 06.07.2006 01:52:

>> I was already thinking about different concepts how to bring more
>> "intelligence" into caching behaviour of one extension. This solution
>> looks
>>  very nice to read.
>>   
> I have been thinking, bu not came up with a good concept yet.
> it means that typo3 core can ask an extension if he has updated content.
> If not typo3 core can use cached content per extension.
> 
> Reason:often a extension can now quickly if content has been changed,
> however generation content takes much time. So when typo3 core can ask if a
> extension has new content only that functions needs to return TRUE from a function
> (can be any class or file).

I think the problem is that TYPO3 does not know what TYPO3 features the
extension will need. There is a huge overhead of loading the whole
"TYPO3-framework" including all global variables, objects and stuff
(fe_users, page-object, etc), so that the USER_INT or extension can
potentially use it. This is a reason why having a single USER_INT in the
page already makes it load many times slower (even if the USER_INT does
nothing at all!).

Imagine the BASKET-view of a shop extension which is shown on every
page. Of course the extension knows when this information changes (when
the user adds or deletes something to its basket). But it has to know
which is the current user and have access to its current session. TYPO3
cannot know what data the extension will need and will have to load
everything. So it might be that the overhead of checking if the basket
has changed and display a cached basket view or just generate a new
basket view isn't that different.

My idea would be that an extension should be able to tell TYPO3 which
features of the core it will need. We have to analyse what are the top
performance killers of the TYPO3-framework and have them optionally not
load if not needed. This is something similar to the eID approach, where
you start with nothing and have to load the framework yourself, if you
need it. But it needs to be more simple and also available for plugins
that are included in the regular index.php.

Cheers,
Ernesto