#14399: Site's get_current() not thread safe? ---------------------------+------------------------------------------------ Reporter: Kronuz | Owner: nobody Status: new | Milestone: Component: Uncategorized | Version: 1.2 Keywords: | Stage: Unreviewed Has_patch: 0 | ---------------------------+------------------------------------------------ Is the Site caching system thread safe? I don't think it is. The patch in Ticket #7517 (as well as the code for get_current()) will get invalid or deleted sites when Site objects get deleted/updated in other thread other than the one using get_current(), since the objects wont get invalidated from such other threads to the one making the request.
I would believe shared memory is needed for that, to invalidate the object in all threads (it can be done using a "sync" time in a shared memory medium (memcache even)) -- Ticket URL: <http://code.djangoproject.com/ticket/14399> 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-upda...@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.
