[TYPO3-ect] Challange: design and implementation of advanced caching

ries van Twisk typo3 at rvt.dds.nl
Sun Jul 8 16:47:14 CEST 2007


I agree with Jan-Hendrik,

I think it might be worth while to check if it is possible
to cache TSFE .

Usually extension can generate there HTML bit's and pieces very fast,
But they to execute them they need to slow and clumsy TSFE and related,
classes and arrays.

Would it not be possible to start caching that?

Ries


On Jul 8, 2007, at 9:35 AM, Jan-Hendrik Heuing [DD] wrote:

> Hi Elmar and others!
>
> I'd like to add some info here. Caching is for speeding up things  
> as you
> know. If you want to speed up things properly, today you end up  
> with a fully
> cached page. If you're now going to add a single USER_INT, the whole
> typoscript engine and such needs to be loaded. And while this bit  
> can be
> very small and simple, the time generating the page increases  
> dramatically.
>
> A slightly different approach would be available to work around it:  
> While
> tsref says PHP_SCRIPT_EXT should not be used anymore, it would give  
> you what
> you need: Caching the whole page, but running individual PHP  
> without loading
> typoscript engine etc...
>
> So one could make use of PHP_SCRIPT_EXT or something new which is  
> taking the
> same routes, query for teasers and such, and then decide what to  
> do: Load
> some ts-stuff, or just display.
>
> Jan-Hendrik
>
> "Elmar Hinz" <elmar.DOT.hinz at team.MINUS.red.DOT.net> schrieb im  
> Newsbeitrag
> news:mailman.1.1183853395.23784.typo3-team-extension- 
> coordination at lists.netfielders.de...
>> Hi,
>>
>> today USER objects are cached as part of the whole page, while  
>> USER_INT
>> are
>> not cached at all. Something in between could bring new features for
>> TYPO3.
>> Think of something like news of google. Each news element is  
>> cached. The
>> personalized page is dynamically combined of the cached elements. The
>> cached elements themself can be updated in defined intervals.  
>> Instead of
>> caching whole pages, caching can be modularized.
>>
>> USER_INT are exectud in a second phase after the page has been  
>> rendered
>> and
>> cached (the marker trick). I am thinking of a cache for objects  
>> within
>> this
>> second phase.
>>
>> We want people for the following steps:
>>
>> a) You have a vision of an advanced object based caching system. You
>> contribute a conception how it looks like and how it should be
>> implemented.
>>
>> b) You implement this within lib.
>>
>> c) You design a TS API, so that it can be set up and used also  
>> with TS.
>>
>> d) You implement it as TS object.
>>
>> Anybody?
>>
>> Regards
>>
>> Elmar
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> _______________________________________________
> TYPO3-team-extension-coordination mailing list
> TYPO3-team-extension-coordination at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team- 
> extension-coordination



More information about the TYPO3-team-extension-coordination mailing list