#26463: Allowing Callbacks/Handlers to be called on Cache entry Expiration
-------------------------------------+-------------------------------------
Reporter: oneTimePad | Owner:
| oneTimePad
Type: New feature | Status: closed
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => wontfix
Comment:
I think the feature is too specialized for inclusion in Django. You could
ask on the DevelopersMailingList to see if anyone else feels it's an
appropriate use of a cache, but I'm skeptical. There are probably better
ways to solve the problem in the linked ticket than this idea. Also
requiring file-based or local memory caching in production is a bit
impractical.
--
Ticket URL: <https://code.djangoproject.com/ticket/26463#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.463914fea5ea54a6f70ed7f24747200a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
