#30072: get_current cache uses global variable instead of cache breaking
multiple
instance deployments.
-----------------------------------------+------------------------
Reporter: lseelenbinder | Owner: nobody
Type: Bug | Status: new
Component: contrib.sites | Version: 2.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
I use the Sites framework extensively with a multiple instances of the
application server deployment of Django. Because the sites framework uses
a global to cache the current site, any update ''only'' affects whichever
application server handled the update, leaving the outdated information
cached on any other application servers.
I would patch it to use the Django caching system instead of a global, but
I'm not sure if that's the correct way to go about it.
--
Ticket URL: <https://code.djangoproject.com/ticket/30072>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.17ac4370d15dee4ba73a667485fbd5a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
