Opened 8 years ago
Closed 8 years ago
#27166 closed Cleanup/optimization (worksforme)
Documentation clarification of warning for using cache-based sessions
Reported by: | Dolan Antenucci | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.10 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
In the 1.10 version of the Using cache sessions documentation, it warns the user that, "You should only use cache-based sessions if you’re using the Memcached cache backend."
From what I understand, other cache backends like Redis work as well as Memcached for this use case. Assuming my understanding is correct, the documentation should be updated to reflect this.
If I'm incorrect, perhaps add a note about why Redis is not a viable candidate.
Change History (3)
comment:1 by , 8 years ago
Easy pickings: | set |
---|---|
Summary: | Documentation clarification on warning for using cache-based sessions → Documentation clarification of warning for using cache-based sessions |
comment:2 by , 8 years ago
comment:3 by , 8 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Type: | Uncategorized → Cleanup/optimization |
Note:
See TracTickets
for help on using tickets.
Django doesn't ship a Redis cache backend so the warning is merely limited to the cache backends shipped with Django. Clearly, we cannot assess the entire possibility of third-party cache backends. Do you feel this needs clarification?