Bug #17

Optimize reflection usage by introducing a cache

Added by Robert Lemke over 12 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Reflection
Start date:
Due date:
% Done:

0%

PHP Version:
Has patch:
Complexity:

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 almost 12 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