[TYPO3-core] RFC #17693 performace of cachingframework: alternative dbbackend

[Helmut Hummel]

Hi,

Ernesto Baschny [cron IT] wrote:
>
> Ok, understood! The creation of the caching tables is *not* an API but
> has to be done individually by each extensions.
>
> Doing a diff between your implementation and the original dbbackend
> reveals very little places which needed the change.
>
> So I would suggest to add a new option to be passed to the dbbackend
> when creating a cache ('usesExpireField = TRUE'), which tells the engine
> if there is a "lifetime" or a "expires" field (you just need to have a
> method called "setUsesExpireField($value)" for this to be handled by the
> abstract class).
>
> The dbbackend could then by default use the old scheme (backwards
> compatibility), and use the new scheme if passed the option. Maybe even
> deprecate the use of caches without this option in future.

When talking about changes to the caching framework, please mind that 
this thing is a backoprt of FLOW3. So any changes we need for TYPO3 v4 
might be relevant for FLOW3 also.

I don't think it is a good idea to drift away too much from the original 
codebase (FLOW3).

Kind regards,
Helmut

-- 
Helmut Hummel
TYPO3 Security Team Leader

TYPO3 .... inspiring people to share!
Get involved: typo3.org