Rename ChainedFastBackend to make it clear that it's about chaining a consistent and inconsistent backend, unlike BackendChain

Created on 29 July 2015, almost 10 years ago
Updated 22 May 2025, 12 days ago

Problem/Motivation

The current naming isn't clear, which is why #2541432: Follow-up for #2231595: Document why ChainedFastBackend cannot use BackendChain β†’ had to add docs to explain the difference. A better name would've made that clear.

Proposed resolution

Fix naming. Go back to the original name @msonnabaum was suggesting perhaps?

Remaining tasks

Do it.

User interface changes

None.

API changes

TBD

Data model changes

None.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

cache system

Created by

πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024