Feature #10439

Data array used in ws-grid should be cached

Added by Marco Bresch over 9 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Workspaces
Target version:
-
Start date:
2010-10-25
Due date:
% Done:

100%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

The hole data array is build at each request. To prevent server time a caching mechanism is needed.

see #10045

10439.patch View (10.7 KB) Marco Bresch, 2011-01-16 22:26

10439v2.patch View (11 KB) Marco Bresch, 2011-01-17 15:13

10439v3.patch View (11.1 KB) Tolleiv Nietsch, 2011-01-18 02:34

10439v4.patch View (1.58 KB) Marco Bresch, 2011-01-18 15:22

Associated revisions

Revision d7bea56c (diff)
Added by Marco Bresch about 9 years ago

Fixed bug #10439: Data array used in ws-grid should be cached

git-svn-id: https://svn.typo3.org/TYPO3v4/CoreProjects/workspaces/workspaces/trunk@3861 743128fe-103e-dd11-99c4-001b210b3e58

Revision 6eb522be (diff)
Added by Marco Bresch about 9 years ago

Fixed bug #10439: Data array used in ws-grid should be cached

git-svn-id: https://svn.typo3.org/TYPO3v4/CoreProjects/workspaces/workspaces/trunk@3864 743128fe-103e-dd11-99c4-001b210b3e58

History

#1 Updated by Marco Bresch about 9 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."

#2 Updated by Marco Bresch about 9 years ago

  • Status changed from New to Accepted
  • Assignee set to Marco Bresch

#3 Updated by Marco Bresch about 9 years ago

  • Target version set to 4.5 Beta 2

#4 Updated by Oliver Hader about 9 years ago

  • Target version changed from 4.5 Beta 2 to 4.5 Beta 3

#5 Updated by Marco Bresch about 9 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.

#6 Updated by Tolleiv Nietsch about 9 years ago

  • Target version changed from 4.5 Beta 3 to 4.5 RC1

#7 Updated by Marco Bresch about 9 years ago

  • File 10439.patch View added
  • Status changed from Accepted to Under Review
  • % Done changed from 70 to 100

#8 Updated by Marco Bresch about 9 years ago

use the caching mechanism only when new caching framework is active

#9 Updated by Tolleiv Nietsch about 9 years ago

#10 Updated by Marco Bresch about 9 years ago

  • Status changed from Under Review to Resolved

commit to trunk (rev. 3860)

#11 Updated by Marco Bresch about 9 years ago

As Susanne mentioned in our Workspace-List I changed the UseCachingFrameworkChecks to real boolean checks (see 10439v4.patch). commited to trunk (rev. 3864)

#12 Updated by Michael Stucki about 6 years ago

  • Category set to Workspaces

#13 Updated by Michael Stucki about 6 years ago

  • Project changed from Workspaces & Versioning to TYPO3 Core
  • Category changed from Workspaces to Workspaces
  • Target version deleted (4.5 RC1)

#14 Updated by Benni Mack over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF