#15894: SITE_CACHE does not invalidate in multiprocess environments
--------------------------------+-------------------------------
Reporter: Kronuz | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: contrib.sites
Version: 1.3 | Severity: Normal
Keywords: cache invalidation | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
--------------------------------+-------------------------------
In a configuration where multiple python processes are created to serve
requests, a global variable contrib.sites.models.SITE_CACHE is created for
each process. In the scenario where each and all processes have used (and
cached) any given Site object; if a client requests the update of the
object (either by saving or deleting the object), only the SITE_CACHE in
the process which served the client request gets invalidated. All other
processes maintain the cached version of the object in their own
SITE_CACHE dictionaries and further calls to get_current() by client
requests in any of those processes return outdated objects.
Instead of using a global dictionary, I suggest using the django caching
system.
--
Ticket URL: <http://code.djangoproject.com/ticket/15894>
Django <http://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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
