I've considered building this kind of thing into my client, but it
feels kind of wrong, so it hasn't been much of a priority. It'd be
impossible to get right without changing the way memcached works, but
one could get close.
--
Dustin Sallings (mobile)
On Apr 2, 2008, at 12:53, "Kris Drebin" <[EMAIL PROTECTED]>
wrote:
Wow, Brian this is fantastic!
My applications are Java apps. I'm not sure exactly how they interface
with the daemon.. My responsibility is just setting up the daemon..
Can a Java app interface with the existing development branch you're
referring to? I would love to help beta test.
Thanks,
Kris
On Wed, Apr 2, 2008 at 12:48 PM, Brian Aker <[EMAIL PROTECTED]> wrote:
Hi!
On Apr 2, 2008, at 12:45 PM, Kris Drebin wrote:
Do you, or does anyone else have any other ideas of how I can
accomplish my goal of creating a fail-over solution using memcached?
so that if one memcached server dies, the other will have all the
needed information?
We have replication support in nodes available as a branch in
libmemcached
right now:
http://tangent.org/552/libmemcached.html
Support is only partially available in the C/C++ versions of the
API. Once
I have them stabilized I am assuming the perl/python/php/ruby
drivers will
come along for the ride.
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
--
Kris Drebin
Adaptavant IT Department Manager
Phone: 1-801-559-3840
Cell: 503-913-9051
