On Wed, Mar 12, 2014 at 12:43 AM, dormando <dorma...@rydia.net> wrote:
> > > > https://github.com/unrtst/Cache-Memcached/tree/20140223-patch-cas-support > > > > This started as just wanting to get a couple small features into > Cache::Memcached, but I ended up squashing a bunch of bugs (and merging > bugfixes > > from existing and old RT tickets), and kept adding features. > > > > The repo above includes: > > * benchmarks (to make sure i didn't slow it down) > > * utf8 key fixes > > * utf8 value support > > * compress_ratio > > * compress_methods > > * serialize_methods > > * hash_namespace > > * max_size > > * digest_keys_method and digest_keys_enable > > * digest_keys_threshold > > * touch > > * server_versions > > * cas, gets, gets_multi > > * cas patch for GetParserXS: > https://github.com/unrtst/memcached/tree/master/trunk/api/xs/Cache-Memcached-GetParserXS > > > > All of those are available under Cache::Memcached::Fast except for the > digest_keys* items. There's some public and open debates regarding whether > > or not using a digest as the key is a good idea, but I want to use it, > and having the option is virtual free, so I included it. > > Cache::Memcached::Fast::Safe automatically uses a digest if the key > length exceeds 200 characters, so it's not without precedent. > > > > I plan on adding ketama (aka consistent hash) support very soon. > > > > It's probably still advisable to point users to Cache::Memcached::Fast > or Cache::Memcached::libmemcached, but fixing the bugs in this module and > > bringing it up to feature parity can't hurt. I almost wish I had given > up on C:M and used one of the others instead, but this has been rewarding in > > its own way. > > > > It would be nice to see these make it to a CPAN release... anyone know > who to reach out to for that (one of the RT tickets had said to come here)? > > > > I'd also welcome any additional review of the branch. > > > > Thank you, > > -- > > Josh I. > > I should probably just give the thing to you. Would you like me to review > your work and cut releases or, what would be best? > > If you've got a little time, an extra pair of eyeballs never hurts. Otherwise, I'd be happy to co-maintain and cut releases (user "unrtst" on pause/cpan). -- Josh I. -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
