On Fri, May 13, 2016 at 6:23 AM, Mehdi Abaakouk <sil...@sileht.net> wrote:
> On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote: > >> What's wrong with pymemcache, that we picked for tooz and are using for >> 2 years now? >> >> https://github.com/pinterest/pymemcache >> > > Looks like a good alternative. > > -- > Mehdi Abaakouk > mail: sil...@sileht.net > irc: sileht > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > pymemcache is not drop-in replacement for python-memcached, but the cost to wire it up to dogpile is effectively a 1-time cost and would need to be done in general for the way keystone / keystonemiddleware works. It isn't unreasonable to go with this option. pymemcache used to have glaring holes in capabilities, but it seems it is mostly up to par now. --Morgan
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev