[TYPO3-dev] t3lib_cache

[Steffen Kamper]

"ries van Twisk" <typo3 at rvt.dds.nl> schrieb im Newsbeitrag 
news:mailman.4318.1200676351.5304.typo3-dev at lists.netfielders.de...
>
> On Jan 18, 2008, at 12:02 PM, Ingo Renner wrote:
>
>> 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...
>>
>>
>> Ingo
>
>
>
> I would love the so an automated way of doing this so an extension 
> doesn't have to do anything.
>
> It might not be possible because there is no good relation between 
> extension names/tables (or can we use TCA??)
>
> Ries
>

i would agree if it would be easy, i don't see the way that core "analyzes" 
what extension does.
You as an extension developer have to define exactly which behavior is 
intended.
So the easy thing should be to define the rules. How they will be defined 
we'll see.

vg  Steffen