Reword session docs on prioritizing "cache" vs "cached_db"
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 a forum question from Tim Schilling about migrating between cache servers with the "cache" backend, which is not easy.
Change History
(7)
| Triage Stage: |
Unreviewed → Accepted
|
| Owner: |
changed from nobody to Joseph V Zammit
|
| Status: |
new → assigned
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
OK, thanks Adam, happy to look at a re-phrasing.
I think there's some value in mentioning that Redis is persistent under standard configurations, so as not to mislead, whilst we're here.