Bug #56319
closed
-1, imho we should keep this separation as long as flow does not merge cacheManager and cacheFactory into one. also, cache is a "connection" class between cms and flow code, so we should keep it for separation, too.
- Status changed from New to Rejected
Imho, this area is not a real bottleneck and it does not make much sense to sacrifice architecture in favor of (negligible) more performance.
For now, I'll close this issue as rejected.
- Status changed from Rejected to New
- Target version set to 7.4 (Backend)
- TYPO3 Version changed from 6.2 to 7
We should get this fixed in CMS7.
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40500
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40500
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40500
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40500
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40500
Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40500
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by