Hey ya'll, I noticed that the caching framework does not currently support setting a CACHE_KEY_PREFIX that would automatically be prefixed to any get/set/delete function call in the caching. I would be willing to write the patch, I just wanted to make sure that I was not missing a discussion thread on this topic.
Django currently supoorts COOKIE prefixes, as well as a CACHE_MIDDLEWARE_KEY_PREFIX, but I would find it immensely useful to have a prefix for all cache key entries (i.e. site's sharing a common caching mechanism, with overlapping keys that hold different data) If this idea is appropriate, it shouldn't take more than an hour or so to make a patch for all cache backends. Thoughts? Nowell --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
