Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Heya, I just got it working and I'm playing around with it. I wanted to give you a heads up that there seems to be a typo in the synopsis. "serves" should be "servers" ?

    serves => [ "10.0.0.15:11211", "10.0.0.15:11212", "/var/sock/memcached" ],
  • Hi lestrrat.

    I only discovered your module after I was well into the development of mine. My Memcached::libmemcached module has a different focus to yours. It aims to be a complete interface to the (feature rich) libmemcached library, while also being very fast.

    I always figured that there would be a separate module layered over it to provide a Cache::Memcached compatible interface.

    Once Memcached::libmemcached gains sufficient features perhaps you'd consider refactoring your module to use Memcached::li

    • I personally have no problem going that route, the only reason I took the other route is because I didn't know if Module::libmemcached was going to be released any time soon. I figured you might eventually come around to releasing it, but at the same time I wanted to try to see just how good libmemcached was, like, now :)

      I suppose the only concern I have is just how much impact it would have as far as performance goes, to have another layer between Cache::Memcached::LibMemcached and libmemcached.
      • Great.

        Re performance, I think I have a reputation for being paranoid about performance :)
        We'll have to see how things work out in practice.

        Meanwhile I'm glad your module exists as it takes the pressure off me to support the Cache::* API in the short term. Thanks.