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
extending proxies with the actual backend? #123
Comments
Michael Bayer (zzzeek) wrote: just an .actual_backend accessor? sure |
jvanasco (jvanasco) wrote: attempt #1 is https://bitbucket.org/zzzeek/dogpile.cache/pull-requests/65 |
Michael Bayer (zzzeek) wrote: OK, I'm travelling the rest of the week so, will try to get to this next week. |
jvanasco (jvanasco) wrote: have a great trip! |
jvanasco (jvanasco) wrote: just adding to this ticket a link to a writeup on the use-case scenario: I needed to start working with the raw redis client to accomplish some work via lua scripting. https://gist.github.com/jvanasco/7ee03c118885bd06e25b651e3139f606 |
Michael Bayer (zzzeek) wrote: added CacheRegion.actual_backend Added method :meth: Change-Id: I91cb858b233bae642c47178e2e7a780b2fef801c → ccfa1ba |
Changes by Michael Bayer (zzzeek):
|
Migrated issue, originally created by jvanasco (jvanasco)
In several situations, I must access the actual backend of a dogpile region which has multiple proxies applied by
wraps
.i've usually been handling it during setup by caching the value onto the topmost object after configuring the region. I derive the actual backend via...
i think accessing this is useful to enough people, so I propose extending wraps/ProxyBackend to track the final proxy/actual backend on the object within dogpile itself.
I am willing to generate a PR, but if there are objections to this I won't bother.
The text was updated successfully, but these errors were encountered: