Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache backend type is forced #25

Open
Didstriker opened this issue Sep 28, 2022 · 1 comment
Open

Cache backend type is forced #25

Didstriker opened this issue Sep 28, 2022 · 1 comment

Comments

@Didstriker
Copy link

I am adding a redis server on my Typo3 instance, which uses this plugin, so I'm trying to move as many caches as possible into the redis service, but for this extension would be impossible without breaking the clear cache functionality.

Due to this extension use a custom cache backend class "ReverseProxyCacheBackend", which extends from Typo3DatabaseBackend, it forces the user to use a database backend, with no other option available.

Would it be possible to use a hook instead of extending a cache backend class?
Similar to what was done for this FrontendHook

Other possibility could be doing a decorator pattern instead of using inheritance

@bmack
Copy link
Member

bmack commented Oct 9, 2023

The main reason we used the DB Backend and extended it was that we had full control over fetching all contents (= all URLs) via the Cache Backend.

See https://github.com/b13/proxycachemanager/blob/master/Classes/Cache/Backend/ReverseProxyCacheBackend.php#L150

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants