Feature #10439
closedData array used in ws-grid should be cached
Added by Marco Bresch about 14 years ago. Updated about 6 years ago.
100%
Description
The hole data array is build at each request. To prevent server time a caching mechanism is needed.
see #10045
Files
10439.patch (10.7 KB) 10439.patch | Marco Bresch, 2011-01-16 22:26 | ||
10439v2.patch (11 KB) 10439v2.patch | Marco Bresch, 2011-01-17 15:13 | ||
10439v3.patch (11.1 KB) 10439v3.patch | Tolleiv Nietsch, 2011-01-18 02:34 | ||
10439v4.patch (1.58 KB) 10439v4.patch | Marco Bresch, 2011-01-18 15:22 |
Updated by Marco Bresch about 14 years ago
Eine Bemerkung von Christian die nicht uninteressant ist zum caching:
"Funnily the caching framework can be used by extensions for own caches without forcing the core caches to run through the caching framework (yuck!). This is what for instance extbase does with the reflection cache. All an extension needs to do is to make sure that the factory and manager objects are present. This can be done my asking t3lib_cache::isCachingFrameworkInitialized() and initialize it on false. This must be done in ext_localconf. If $TYPO3_CONF_VARS['SYS']['useCachingFramework'] is TRUE, this is done by the core already."
Updated by Marco Bresch almost 14 years ago
- Status changed from New to Accepted
- Assignee set to Marco Bresch
Updated by Oliver Hader almost 14 years ago
- Target version changed from 4.5 Beta 2 to 4.5 Beta 3
Updated by Marco Bresch almost 14 years ago
- % Done changed from 0 to 70
The caching works but there is still one problem. If a cached item changed then the cache holds the old data. So there is a mechanism needed which flushes the affected cache entries.
Updated by Tolleiv Nietsch almost 14 years ago
- Target version changed from 4.5 Beta 3 to 4.5 RC1
Updated by Marco Bresch almost 14 years ago
- File 10439.patch 10439.patch added
- Status changed from Accepted to Under Review
- % Done changed from 70 to 100
Updated by Marco Bresch almost 14 years ago
- File 10439v2.patch 10439v2.patch added
use the caching mechanism only when new caching framework is active
Updated by Tolleiv Nietsch almost 14 years ago
- File 10439v3.patch 10439v3.patch added
Updated by Marco Bresch almost 14 years ago
- Status changed from Under Review to Resolved
commit to trunk (rev. 3860)
Updated by Marco Bresch almost 14 years ago
- File 10439v4.patch 10439v4.patch added
As Susanne mentioned in our Workspace-List I changed the UseCachingFrameworkChecks to real boolean checks (see 10439v4.patch). commited to trunk (rev. 3864)
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
- Target version deleted (
4.5 RC1)