Possible merge with Verschlimmbesserung

[aphyr]

So this started out as a layer of code in Jepsen around etcd-clojure, then clj-etcd, then things got a little out of hand and somehow became a full-blown client. I felt bad about submitting it as a pull request to either project because there are so many breaking differences; but wanted to let you know that this thing is now out there, and you can cannibalize ideas from it if you're so inclined. It's missing watches, leaders, and locks, but I'm relatively happy with the core kv API and semantics.

Thoughts? Should I finish porting features from clj-etcd to Verschlimmbesserung? Would you like to consume part of Verschlimmbesserung into your codebase? No real strong feelings here; happy to keep the fork if you think both are valuable. :)

[rthomas]

Hey mate, sorry for the delay :)

Happy to merge them together, I'd rather we combine and focus on the one client than maintain multiple clients.

Thoughts on the best way to do this?

[aphyr]

Howdy there Ryan! I put some additional work into the error handling and CAS semantics for Verschlimmbesserung, and am pretty happy with its behavior at this point, but I'd also like to include the watch/leader/lock support from clj-etcd. Maybe it'd be most straightforward to port those clj-etcd features into V? Most of the options handling/URI infrastructure is all ready to go. :)