Some time ago, I pondered the possibilities for sharing the dbsettings cache across multiple processes in Apache and elsewhere. I ended up just using Django's cache framework, and I finally received confirmation that it does work properly. However, my original assumption that locmem isn't multi-process seems to have some support, given the response I got on the ticket (see below).
locmem certainly seems thread-safe, but as far as I can tell, the only place that indicates that it's multi-process is its documentation. I still don't have a multi-process setup with which to do any testing, so I'm relying on the experience of others, and this message is the only message I've gotten on the subject. If it's not multi-process, should it be made so? If not, we should modify the documentation to reflect this. -Gul ---------- Forwarded message ---------- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Jul 16, 2007 3:42 PM Subject: Issue 5 in django-values: incompatibility with mod_python To: [EMAIL PROTECTED] Issue 5: incompatibility with mod_python http://code.google.com/p/django-values/issues/detail?id=5 Comment #7 by [EMAIL PROTECTED]: Thanks for pointing out the different cache backends! It finally worked with db and file backends (and, supposedly, will work with memcached). It did not work with locmem and simple, though (which is strange since locmem claims it is multi-process). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
