I ran into a seemingly common problem with cache key conflicts between two projects that both share an app and the same memcache instance. I would imagine that being able to optionally set a PROJECT_CACHE_PREFIX that is prepended to every key when setting/getting would be a nice transparent way of ensuring there are no conflicts. Obviously if the behavior is to share cache between projects, then no prefix can be specified.
I want to get initial feedback, implications, etc. on this before I start writing a patch. Thanks, -Byron -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
