[TYPO3-project-4-3] 4.3.0 vs. 4.2.7

[Martin Kutschker]

JoH asenau schrieb:
>>> And another question:
>>> Does it really make sense to use a constructor that has to "build"
>>> the backend and frontend used by the CF on each request again and
>>> again?
>>> Why can't we just use ready made files for each possible combination
>>> of cache frontend and backend, which then will be triggered by a
>>> simple matching combination in TYPO3_CONF_VARS instead of such a
>>> "framework"?
>> I'm not familar enough with the CF to get what you mean. Could you
>> explain or give a short example?
> 
> Well - as far as I understand it by looking at the code, the "caching
> framework" is constructed as a singleton on each request.
> During initializazion it checks TYPO3_CONF_VARS which kind of caching
> frontend or backend to use and gets the necessary class files to create the
> appropriate combination for the basic interfaces, which are again classes
> that will trigger other classes etc. pp.
> 
> Since each singleton will be gone after the request ends, this has to be
> done again and again and again, instead of doing it once by creating a file
> called "currentCacheCombination.php" or however you may call it, that could
> be used until the setup in TYPO3_CONF_VARS changes.

I see. BTW, that's true for other classes as well. Maybe we can think
about a strategy to which objects can be created and stored/serialized
instead of being instantiated again and again.

> I will try to dig deeper before providing any patches though.

Good idea.

Masi