Hey Adam and Andrew,
I can definitely make the naming scheme something like get_async() rather
than just get().
> This section specifically says that the default implementations will back
onto the sync methods by default, so built-in cache backends won't need to
all be converted (at once?).
Agreed - there's no work on caching inside Django yet, since the ORM is my next
focus, but I would definitely suggest writing a new pluggable third-party
backend that somehow provides async versions of the methods.
The main work to do here is to work how quite how possible it is to offer all
Hi Andrew
I don't believe any work has started on async caching in core. However
there is a plan in DEP 9, the document that outlines how asynchronous
caching will work, using suffixed methods like get_async() etc. See
https://github.com/django/deps/blob/master/accepted/0009-async.rst#caching
.
Hey guys, I'd like to contribute to the effort to make Django more async
capable. I've started to write an aioredis based cache backend based on
django-redis, but I noticed the BaseCache in Django is still all
synchronous basically.
I was wondering which backends I should make async capable
