All cache backends need to call its 'close' function
|Reported by:||jifeng.yin@…||Owned by:||gnosek|
|Component:||Core (Cache system)||Version:||master|
|Cc:||zsiciarz||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Django currently supports multiple cache backends. However, the only DEFAULT_CACHE will be closed when request is finished, just like before as the single CACHE_BACKEND setting.
Should we apply this logic to all the cache backends? Because several memcache backends are totally possible. Think in this user case: one for dramatic data -> shorter timeout, allow evictions; the other for static data -> longer timeout, do not allow evictions.
Please let me know your thought, thanks!
Change History (6)
comment:1 Changed 5 years ago by aaugustin
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted
comment:2 Changed 4 years ago by gnosek
- Owner changed from nobody to gnosek
- Status changed from new to assigned
Changed 4 years ago by gnosek
comment:4 Changed 4 years ago by zsiciarz
- Cc zsiciarz added
- Triage Stage changed from Accepted to Ready for checkin