Project

General

Profile

Actions

Feature #81435

closed

Story #81432: Replace TYPO3 caching solution with PSR-6 / Doctrine capable alternative

Create shared, base cache configuration affectable by TYPO3_CONF_VARS

Added by Claus Due over 7 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2017-06-02
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Rather than force a TYPO3 database backend and variable frontend as default, it is a simple matter to place this default configuration in TYPO3_CONF_VARS together with the usual cache configurations. Furthermore, so many of the options used in the cache configurations are duplicated and would greatly benefit from inheriting things like default lifetime and default cache pool from a single source of configuration.

This is achievable by loading the default cache configuration from a reserved named configuration and using array_replace_recursive when determining cache configuration to merge the custom configuration on top of the default configuration.

Finally this allows lifting the requirement that a cache must be configured: as long as the default configuration is a workable cache setup, any cache can be created on-the-fly without any problems and will correctly use the ad-hoc identifier (but will only be manually flushable until properly configured).

Actions #1

Updated by Philipp Gampe over 7 years ago

IMHO this should be done even if we do not move to PSR-6. It is a nice feature on its own.

Actions #2

Updated by Gerrit Code Review over 7 years ago

  • 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 https://review.typo3.org/53154

Actions #3

Updated by Gerrit Code Review over 7 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53154

Actions #4

Updated by Gerrit Code Review over 7 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53154

Actions #5

Updated by Gerrit Code Review over 7 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53154

Actions #6

Updated by Gerrit Code Review over 7 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53154

Actions #7

Updated by Gerrit Code Review over 7 years ago

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53154

Actions #8

Updated by Gerrit Code Review over 7 years ago

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53154

Actions #9

Updated by Gerrit Code Review almost 7 years ago

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53154

Actions #10

Updated by Gerrit Code Review almost 7 years ago

Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53154

Actions #11

Updated by Susanne Moog over 5 years ago

  • Status changed from Under Review to New

Patch has been abandoned.

Actions #12

Updated by Christian Eßl about 5 years ago

  • Category set to Caching
Actions #13

Updated by Christian Kuhn almost 3 years ago

  • Status changed from New to Closed

Hey. It seems work in this area is completely stalled since 4 years. A couple of issues have been resolved, the cache API has been streamlined a bit.

I'm about to close the story and related issues for now: They are active action points, but stalled.

I guess if PSR-6 is picked up again, some solution would be different from what has been worked on 4 years ago. If single issues are still appropriate, they could be re-opened and re-attached to a new story again. Other than that, there seems to be little value in still keeping them open at the moment.

Actions

Also available in: Atom PDF