#33573: Add native async support to redis cache backend
-------------------------------------+-------------------------------------
Reporter: Christopher Bailey | Owner: Ahmed
| Ibrahim
Type: New feature | Status: assigned
Component: Core (Cache system) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Christopher Bailey):
I do not think have two separate clients is a good approach. It is
actually a really bad one for apps that have a lot of caches. If you have
a legacy WSGI app you want to migrate to ASGI and you have 20 caches (not
as crazy as it sounds for larger apps with very high throughput). Now you
have to duplicate all of them, one for sync and one for async, and have 40
caches?
If a cache is capable of both sync and async, it should raise an exception
when used in the wrong context rather than forcing it to be a
configuration/usage issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/33573#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107019282f12eea-0a9ee2e4-bf59-47ae-9865-a0f47f2096e5-000000%40eu-central-1.amazonses.com.
