sessions.backends.cache does not allow non-default cache to be configured
|Reported by:||Owned by:||Aymeric Augustin|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Django 1.3 introduced support for more than one cache to be defined. However, the cache-based session store backend does not support using a non-default backend.
A configuration option should be available to select the cache to be used by the Django session store cache backend.
Use case: One may want the session store to be kept in a replicated cache (to prevent user-visible disruption during failover events) vs cached data which can be regenerated without user-visible impact beyond performance.
Use case: One may want the session store to be kept in a distributed cache while keeping other content in a system-local cache.
Change History (9)
comment:6 Changed 4 years ago by
|Patch needs improvement:||unset|
|Triage Stage:||Accepted → Ready for checkin|