[TYPO3-50-general] Lighttpd as "standard"

Martin Kutschker Martin.Kutschker at n0spam-blackbox.net
Tue Nov 14 18:09:35 CET 2006

Johannes Reichardt schrieb:
> Hi Masi,
>> Well, built-in is fine. AFAIK, TYPO3 has been changed to set cache 
>> control headers correctly, so admins have already successfuly used 
>> Apaches builtin cache/proxies.
>> If you think that lighttpd needs some more http headers for caching 
>> see if we can add them via hooks. AFAIK there are already some for the 
>> purpose of caching.
> As i see the cache/proxy solutions only cache full webpages - which is 
> great but in en-vogue "web 2.0" applications with logged in users for 
> example
> you have a big mix of static and dynamic most of the time which sucks 
> most performance. I think about something like a session/condition based 
> way
> to return a functions data the normal way *or* from cached static data.
> something like
> <?php
> class my_Componoent {
>    function my_Component() {
>       return t3_core->cache(showUserInfo(),'CACHE CONDITIONS HERE');
>   }
>   function showUserInfo() [
>       return 'foo';
>    }
> }
> ?>

Ok, fine but what has it to do with the webserver? What you're asking for 
is means to store and retrieve data from some "cache service". This could 
be provided by a TYPO3 API. If the API is clean enough you may write an 
extension that uses any APIs that lighttpd may offer.


More information about the TYPO3-project-5_0-general mailing list