#30517: Add Redis cache backend.
-------------------------------------+-------------------------------------
Reporter: dulmandakh | Owner: nobody
Type: New feature | Status: closed
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution: wontfix
Keywords: redis cache | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
It's worth quoting Aymeric's post on the mailing list:
> To move this forwards, my suggestion would be to write a DEP, to flesh
out the rationale for a built-in solution, and to focus on the breadth of
functionality the built-in backend would support. My preference would be a
basic set of features, like the other cache backends. I believe that's
what django-redis-cache does. This will leave room for third-party
packages like django-redis to provide more advanced features. To give a
concrete example, like other cache and database backends, a redis backend
could provide persistent connections but not implement a connection pool.
Until now Django has left the management of connection pools to third-
party packages.
--
Ticket URL: <https://code.djangoproject.com/ticket/30517#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.be2d391e3f9918c9a8d8e09d7e678ac3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
