#15894: SITE_CACHE does not invalidate in multiprocess environments
------------------------------------+------------------------------------
Reporter: German M. Bravo | Owner: nobody
Type: Bug | Status: new
Component: contrib.sites | Version: 1.3
Severity: Normal | Resolution:
Keywords: cache invalidation | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Comment (by khink):
(Replying because we got bitten by this issue recently.)
I've read the proposal at https://groups.google.com/d/topic/django-
developers/OGOf1TfSBBs/discussion, and though it seems like a fine
solution, there doesn't seem to be much movement currently.
I would argue that, in absence of a valid alternative, a patch would be
welcome. I don't think this would be an intrusive change: It could make
the multiprocess envs work without making things more difficult for people
who are happy with the current setup.
Would there be other reasons for not accepting patches that i'm not aware
of?
We'd be happy to invest some time into getting a patch merged in Django.
Currently, we're patching it ourselves.
Regards,
Kees
--
Ticket URL: <https://code.djangoproject.com/ticket/15894#comment:21>
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/064.f07555847ccad736df5632d0f9348708%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
