#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 amirreza):
Replying to [comment:20 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
hi
we discussed it in https://forum.djangoproject.com/t/need-input-for-async-
redis-backend/38426/8
i've also provided some info about some of the problems async caching has,
that need solving.
i think the current idea is to do 3rd party work.
as i mentioned in the forum, i have a pr in `django-valkey` that would do
the work
i'm currently examining it, i'd be glad if i get a review
--
Ticket URL: <https://code.djangoproject.com/ticket/33573#comment:21>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701981de81981-42bd6abd-6341-46b7-b22e-d195e5d3470e-000000%40eu-central-1.amazonses.com.
