Closed bases in memcached, how?

Question

memcached

There is a certain SaaS solution - a cluster of our identical apps. Users can customize the functionality by overlaying php files with their own. The data is stored in MySQL, respectively, the login / password / database is different for everyone, while everything is secure, but slow.
It is necessary to configure cache storage in memcach(e|ed), but in such a way that some apps cannot see/change someone else's cache. The solution with different memcache ports is not suitable, there are too many.
The very first thing that comes to mind is working through a single API (proxy pattern), which always checks the conditional access parameters. The simplest kind is the secret prefixes of the keys (say sha1).
What would you choose/suggest? :)

Answer 1

give your memcache api and use salt when working with keys.

Answer 2

I met with such a problem, I solved it by adding the so-called salt key to the names , which was a unique identifier for the entire program.
$memcache->set($prog_sol.$name,

Answer 3

In my mind, a simple authentication was recently screwed to memcached, but I didn’t find anything about it right off the bat, maybe it will do?
code.google.com/p/memcached/wiki/ReleaseNotes144