meta_storage is a dict and a class variable (there is only one for all apps). Given one app meta_storage[app] is the dictionary that stores that cache for that app.
You do not need this if you use a third party cache system but make sure the generated keys includes a prefix that avoids conflicts between apps. On Sep 6, 6:42 pm, Niphlod <[email protected]> wrote: > 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 tohttps://github.com/andymccurdy/redis-pyconnections 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 ?
