Bug #17

Optimize reflection usage by introducing a cache

Added by Robert Lemke over 8 years ago. Updated almost 5 years ago.

Status:Closed Start date:
Priority:Should have Due date:
Assigned To:Robert Lemke % Done:

0%
Category:Reflection
Target version:TYPO3 Flow Base Distribution - 0.1
PHP Version: Complexity:
Has patch: Affected Flow version:

Description

As reflection is used in many parts of the Component Manager and the AOP Framework, it might make sense to create some clever way of caching Reflection objects. While the results of the AOP Framework (the proxies) will be cached anyway, the Component Manager still does class reflection for finding component type implementations (source:Packages/Core/Classes/ComponentManager/T3P_Core_ComponentManager.php).

History

#1 Updated by Robert Lemke over 7 years ago

  • Status changed from New to Closed
  • Sprint set to wontfix

We probably don't need caching on that level, but better try to cache the component configuration etc.
Close for now ...

Also available in: Atom PDF