I like the ideas of your proposal, it seems very natural to use
Callable/Future for zk operations rather than something with more
opaque semantics (does this method block? etc.). Let's discuss this
more, I'd be more than happy to help out.
We're still using 3.2.1 so I'll probably have to fix zkclient when we
upgrade in the near future.
On Wed, Jul 14, 2010 at 12:49 AM, Thomas Koch tho...@koch.ro wrote:
ZkClient (http://github.com/sgroschupf/zkclient) provides a nice wrapper
around the ZooKeeper client and handles things like retry during
ConnectionLoss events, and auto reconnect. Does anyone (other than Katta)
use it? Would people recommend using it? Thanks,
I have some ideas for an alternative Zk Client design, but haven't had the
time yet to hack it together:
I don't like zkClient very much, but it's the best thing available by now
AFAIK. Also have a look at this bug:
Thomas Koch, http://www.koch.ro