[TYPO3-mvc] Autoloader and Cache
Steffen Kamper
info at sk-typo3.de
Thu Jul 30 21:30:17 CEST 2009
Hi Sebastian,
Sebastian Kurfürst schrieb:
> Hi Steffen,
>
>> _Autoloader_
> The reason for including it in Localconf was that if you have an Extbase
> extension and call custom classes via TypoScript, you should not need to
> explicitely include the library, but the aim was that it "just works".
>
hm - i have to think about. But in this typoscript, an extension is
addressed, so TX_ could help to find out.
>> extbase autoloader is instanciated before core
>> autoloader, which means that it will be used at first place.
> Isn't that a bug? :-) I'd expect that the core autoloader kicks in
> first, and then it should not be a performance issue either.
>
it is - that's the reason i ask. from my first view localconf are read
first, so extbase kicks in first. I will do some reproducable tests.
I also suggest a registration list which improves performance a lot vs
string manipulations, but it's another issue.
>> _Cache_
>> is there a reason why file cache is used here? Why not store this in one
>> of the cache tables, or in a new cache table?
> Yep, go ahead and change this :-) I'm not all too familiar with the
> cache, so I'd welcome every contribution there!
>
can you give me a hint which kind of cache is written and who writes it
(maybe where)?
I come up with a patch using an own table. After, user can decide and
configure with cache framework, if he like another cache handling for this.
vg Steffen
More information about the TYPO3-project-typo3v4mvc
mailing list