[TYPO3-core] Announcing TYPO3 CMS 6.1.0 Alpha1

Christian Kuhn lolli at schwarzbu.ch
Tue Mar 19 18:55:21 CET 2013


On 03/19/2013 05:41 PM, Alexander Opitz wrote:
> The Number of classes is not the problem, but the Number of classes with
> an alias for BC ... it is to much.

Another idea:
The main file<->location cache file that is created by the autoloader 
grows with the usage. So, if you click somewhere, if new class is found 
in the system that is not in the direct cache file yet, it will be added 
(and the new cache file persisted in shutdown()). That means fe 
performance degrades if you for example click around a lot in the 
backend until "all" locations are known.

Possible solution:
- Create a FE (TYPO3_MODE === FE) and a separate backend (or: all other 
scopes) file ... should be easy to implement.
- Another idea is to cache to a 'small fe file first' that consists of 
all files needed for full cache scenario but not more. If frontend 
switches to no_cache or some user_int needs to be resolved, it gives the 
autoloader a signal to switch to a second FE 'big' cache file to gather 
everything that is needed in those cases. The second solution is 
probably a bit harder to implement due to the FE code structure ...


More information about the TYPO3-team-core mailing list