Feature #81455
closed
Story #81432: Replace TYPO3 caching solution with PSR-6 / Doctrine capable alternative
Add identifier locking capabilities to TYPO3 cache frontends
0%
Description
Rather than force the consumer to implement locking to prevent multiple threads from generating the same cached content (i.e. TSFE during page generation), it is a simple matter to fit any caching frontend with locking capabilities that reserve an identifier and forces all other threads than the cache generating one, to wait for the lock to be released before continuing.
This feature can then be used in several places in TYPO3 to reduce issues with cold caches - and can replace the current page cache locking procedure.
Updated by
Updated by Christian Kuhn about 2 years ago
- Status changed from New to Rejected
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.
Updated by Christian Kuhn about 2 years ago
- Status changed from Rejected to Closed