#32076: Adding async methods to BaseCache
-------------------------------------+-------------------------------------
Reporter: Andrew Chen Wang | Owner: Andrew
| Chen Wang
Type: New feature | Status: assigned
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution:
Keywords: cache | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andrew Chen Wang):
> The cache closing problem is a bit larger, though
I wanted to put this in a separate comment because, while writing my PR
comment, the issue of adding async cache to Django might be larger but
this ticket is important in order to start porting the rest of Django to
async. Lots of things like the SessionCache backend and generally closing
the cache using Signals requires adding a lot of code; without those async
methods i.e. this ticket, we can't actually implement the code that uses
the cache.
To me, if DEP 9 is to implement Django templates, middleware, signals,
etc. as asynchronous, the base layer of the cake needs to be set first:
that means getting the cache and database access ready.
--
Ticket URL: <https://code.djangoproject.com/ticket/32076#comment:7>
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/074.773150f32d88d41d86114f106ded59c1%40djangoproject.com.
