I ran into a problem with Django's caching backend when using memcache and threads. Instances of memcache.Client are not thread-safe, and Django creates a single instance shared by all threads. I wanted to post this here rather than report a bug since it's not necessarily a bug in Django; however, memcache.py isn't really to blame either.
The issue came up while running through fastcgi. The keys and values where being swapped/mixed up which led to seemingly impossible errors. It wasn't really much of an issue since I just switched to a preforked. I also would like to thank everyone who's contributed to Django. I couldn't imagine web development without it! - Samuel --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
