Add object-cache awareness for persistent backends #32
Labels
No labels
area: build
area: ci
area: compare
area: model
area: plugin
area: provenance
area: rite
area: settings
area: ui
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Ordo#32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Sites with a persistent object cache (Redis/Memcached) should benefit from it, while sites without one still work via the database transient store. The caching layer should not assume a backend.
Acceptance criteria
Notes
Transients automatically route to the object cache when one is installed; verify keys are grouped sensibly.