multiple sites on one memcached

[urban]

For every site which use for example CacheMiddleware we need to run new memcached instance, its not efficient with few small sites. I think that adding a key_prefix to the CACHE_BACKEND params will solve this problem. I've attached patch aganist memcache backend.

[Thomas Kerpe]

What about just using CACHE_MIDDLEWARE_KEY_PREFIX?

​http://www.djangoproject.com/documentation/settings/#cache-middleware-key-prefix
​http://www.djangoproject.com/documentation/cache/#the-per-site-cache

I understand that will exactly solve the issue so I'm closing the ticket.
If that's not the issue feel free to reopen and comment.

[urban]

It solves some problems, but not all, cache can be also set in other (than the CacheMiddleware) aplications, so maybe reimplement it in the cache framework instead of only in CacheMiddleware?

[Thomas Kerpe]

With only this informations the issue is invalid since it describes no bug or new feature.
Describe it clearer maybe with a testcase.

[(none)]

Milestone post-1.0 deleted

[mordicuac]

Using cached_db backend for session sharing memcached with diferent django sites may create session_id conflicts in memcached, using CACHE_MIDDLEWARE_KEY_PREFIX in cache backend solve it.

[Russell Keith-Magee]

A site-wide cache prefix was added in [14623]