-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
Fixed non-cache stuff for memcached #133
Conversation
This allows you to specify any cache. If a redis-type cache with a pipeline is used, you get pipeline support. If not, the cache will still be used, but without atomic transactions.
@007 Thanks for the PR, a few questions.
|
@CodeMonk could speak to it better than I can, but I'll give it a go.
|
@CodeMonk @007 I'm fine with supporting different backends, as long as they work as planned and are fast, and we have tests to prove they work now, and won't break in the future if something changes. I didn't know that Memcached supports the touch, keys commands, is that a new feature? Any chance you could add some tests mockcache tests? |
@kencochrane Memcached does NOT support keys, but, I believe it supports touch (by updating the expiry) Far as I know, key listing and pipeline are the only unsupported features between memcached and redis. I'll start working on some tests . . . |
Where are we with this PR, if we are no longer going to make the change let’s close it. If this is a feature people want, we will need someone to take over and make the changes needed to get it merged. Any volunteers? |
Sorry - a huge change came in before my PR was approved. I'm running live with the code from my PR, but, I haven't had a chance to refactor for the changes upstream. I'll close the PR for now. |
Or you can close - I may not have perms. |
This allows you to specify any cache. If a redis-type cache with a
pipeline is used, you get pipeline support. If not, the cache will still
be used, but without atomic transactions.