On 4/3/07, Nowell Strite <[EMAIL PROTECTED]> wrote: > Since it would be a global prefix, it would be transparent to the > Django developer (if you want to assign your own prefix, then leave > the settings.CACHE_KEY_PREFIX blank and do it yourself-- > cache.set(settings.MY_CACHE_KEY_PREFIX + key, value)... but since you > will always want to prefix your cache keys (in the case of a shared > caching mechanism) I think it would be beneficial to implement this-- > we already do for set_cookie/get_cookie/delete_cookie, so why not > here?
I can see the value of a global CACHE_KEY_PREFIX setting, but we're always hesitant to add new settings. What if we removed the CACHE_MIDDLEWARE_KEY_PREFIX, in favor of a new CACHE_KEY_PREFIX setting? Is there a case where the two settings would need to differ? Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
