[TYPO3-dev] t3lib_cache

[Steffen Kamper]

"Ernesto Baschny [cron IT]" <ernst at cron-it.de> schrieb im Newsbeitrag 
news:mailman.1.1200678180.17799.typo3-dev at lists.netfielders.de...
> Ingo Renner wrote: on 18.01.2008 18:02:
>> Ernesto Baschny [cron IT] wrote:
>>
>> Hi Ernesto,
>>
>>>> Why only single views?
>>>> if a record is changed, then also a list view can be changed, right?
>>>
>>> Yes, but which? A list view showing the 5 "latest" news in category ABC. 
>>> How will a single record change affect that cache? What about a *new* 
>>> news record? Will it appear on that page? Depends on its timestamp and 
>>> on the category it is in etc. Maybe a record is updated, it was on 
>>> category XY, now it is also on category ABC. Only the extension itself 
>>> knows where this record might appear. This is what I was trying to 
>>> explain, why it is not so simple for TYPO3 core to know what caches to 
>>> clean on a simple record changes (or on expiration of endtime).
>>
>> Well, an extension would then need to hook into TCEmain and watch for its 
>> records to run by as they get created or changed. When this happes the 
>> extension needs to take care of marking certain parts of the cache as 
>> "dirty". This should all be very simple for extension developers by using 
>> an API - otherwise if it isn't easy, they won't use it...
>
> All agreed! But still difficult.. :)
>
> Cheers,
> Ernesto

cache is and will be a difficult task, also with an API.

It's on us to provide also a good documentation and handy examples, then 
developers will use these techniques.

vg  Steffen