I think I have a first working draft for using redis as a backend for cache like gluon.contrib.memcache ....
I dind't get completely the internals of cache, though ..... storing with 'predefined' keys works ok, and also the expire works out of the box. I removed the mutex lock found in other cache backends because I think redis ensures atomic operations and avoids conflicts "out of the box". According to https://github.com/andymccurdy/redis-py connections are managed by the module itself , but that needs testing (I can see connections created and dropped regularly, so it's not leaking incrementally, but on overloaded systems I can't tell) Caching values with fixed keys works, caching selects works, use as decorator works .... I didn't quite get all the self.meta_storage use .... can someone explain to me ?
