#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 Changed 23 months ago by Dolan Antenucci

Easy pickings: set
Summary: Documentation clarification on warning for using cache-based sessionsDocumentation clarification of warning for using cache-based sessions

comment:2 Changed 23 months ago by Tim Graham

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?

comment:3 Changed 23 months ago by Tim Graham

Resolution: worksforme
Status: newclosed
Type: UncategorizedCleanup/optimization
Note: See TracTickets for help on using tickets.
Back to Top