dogpile.cache would be substantially lighter on the client-side as it only has a hard dependency on dogpile.core. It supports plenty of backends beyond memcached and we already use it in keystone quite heavily. http://dogpilecache.readthedocs.org/en/latest/ On Mon, Mar 31, 2014 at 11:35 AM, Doug Hellmann <doug.hellmann at dreamhost.com > wrote: >>>> On Mon, Mar 31, 2014 at 12:18 PM, Kurt Griffiths < > kurt.griffiths at rackspace.com> wrote: >>> Hi folks, has there been any discussion on using oslo.cache within the >> auth_token middleware to allow for using other cache backends besides >> memcached? I didn’t find a Keystone blueprint for it, and was considering >> registering one for Juno if the team thinks this feature makes sense. I’d >> be happy to put some time into the implementation. >>>> That does make sense. We need to look at the dependency graph between the > keystoneclient and oslo.cache, though. It appears the current version of > oslo.cache is going to bring in quite a few oslo libraries that we would > not want keystoneclient to depend on [1]. Moving the middleware to a > separate library would solve that. >> [1] https://wiki.openstack.org/wiki/Oslo/Dependencies >> Doug >>> _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140331/642b68f0/attachment.html>