#33797: Reword session docs on prioritizing "cache" vs "cached_db"
------------------------------------------------+------------------------
Reporter: Adam Johnson | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.sessions | Version: dev
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
The "using cached sessions" section of the sessions docs
(https://docs.djangoproject.com/en/dev/topics/http/sessions/#using-cached-
sessions) lists "cache" first and doesn't really emphasize the downside of
its non-persistent sessions. I think "cached_db" should be recommended
first, and "cache" listed only as an option when you have a persistent
database server.
Users getting logged out "randomly" due to a full/ephemeral cache server
is not a good user experience. It also leads to operational complexity.
The example that made me check this was [https://forum.djangoproject.com/t
/changing-session-engine-from-cache-to-cached-db/14421 a forum question
from Tim Schilling] about migrating between cache servers with the "cache"
backend, which is not easy.
--
Ticket URL: <https://code.djangoproject.com/ticket/33797>
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/01070181884e8b5e-161a3a4b-6793-44c7-8918-4eceb76432d4-000000%40eu-central-1.amazonses.com.
