#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 Andrew Chen Wang):
@Ahmed I'm forgetting context since it's been awhile, but my draft seems
to have some ideas: https://github.com/Andrew-Chen-Wang/django-async-
redis/pull/6. Specifically:
1. A lot of the code seems to be copying the sync to async prefixed
classes and methods
2. There are some packages that use the default cache client. It needs to
know whether the client is async/sync capable, so you may need to add some
variable (similar to how middleware classes are async/sync capable via a
variable). The reason I made two classes, one for sync and another for
async, is so that the client caller can know whether to execute as sync or
async. I believe work stalled on my end trying to determine how to resolve
the what context the client caller is coming from.
--
Ticket URL: <https://code.djangoproject.com/ticket/33573#comment:12>
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/0107019282bda0cd-71abf493-21e6-49f9-802f-8ed7146caf77-000000%40eu-central-1.amazonses.com.
