Bug #56320
Epic #55070: Workpackages
Epic #55065: WP: Overall System Performance (Backend and Frontend)
Bug #52949: Speed decrease since 4.5
Bug #56307: Findings from Bootstrap/PackageManager/ClassLoader analyses
Check emptying the Flow Classes as far as possible
| Status: | Rejected | Start date: | 2014-02-26 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | Sprint Focus: | |||
| Complexity: |
Description
remove unused/superfluous code - put the interface in the same file as the the extending ones
in order to avoid requiring and high parsing times for TYPO3\Flow\Package\PackageManager, TYPO3\Flow\Package\PackageFactory and TYPO3\Flow\Package\Package
History
#1 Updated by Thomas Maroschik over 1 year ago
I don't think that will bring us much benefit as these classes are pretty small. It rather streches the gap between CMS and Flow in this regard.
#2 Updated by Mathias Schreiber 6 months ago
- Status changed from New to Rejected