#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 Ahmed Ibrahim):
Replying to [comment:18 amirreza]:
> hi
> i have a feeling this is abandoned, but if not, i'd like to take over
>
> the way i will do it is by using seprate classes for sync and async,
using redis's native support for async, as i explained in my previous
message
>
> this way the issue i riased at #36047 will also be easy to fix (i think)
> i'll tackle #36047 afterwards
> the way i'll do is to check if the backend has an async `aclose` method,
if so, call `async_to_sync()` on it
> tho this one is a raw idea and not totaly sure about it
>
> let me know if this is ok with you
dw I will do it, but I need a Django fellow to provide a certain answer on
which implementation we should go with, since we can do it and it won't
get accepted, I "think" (not sure) I emailed before in the mailing list,
but got no response, I'm not sure if that's deja vu or something
--
Ticket URL: <https://code.djangoproject.com/ticket/33573#comment:20>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019816e908db-7b89692a-1e6b-4222-8b62-e666359dbc79-000000%40eu-central-1.amazonses.com.
