tgockel / zookeeper-cpp Goto Github PK

http://curator.apache.org/curator-recipes/persistent-node.html

The C client's logging leaves a lot to be desired. Since log_callback_fn is simply void (*)(const char *message), we do not have a way to do basic things:

• Quickly post-filter by level
• Use a void* or other user data
• Transform the output in any way that requires context

We probably just want to work around this...or fix the C API's logging.

http://curator.apache.org/curator-recipes/shared-reentrant-lock.html

Need a type for dealing with an actual ZK server. This is critical for testing.

http://curator.apache.org/curator-recipes/tree-cache.html

Add support (meaning: continuous integration testing) for Ubuntu 17.04.

http://curator.apache.org/curator-recipes/distributed-atomic-long.html

Currently, we rely on the package manager to run the ZooKeeper server. However, since this library needs to tested against multiple versions of ZooKeeper, fetching it with Ivy makes a lot of sense.

To create ZNodes, we must specify creation flags via a create_flags enum.

Add support (meaning: continuous integration testing) for Ubuntu 18.04.

This is blocked on Ubuntu 18.04 actually existing.

http://curator.apache.org/curator-recipes/shared-lock.html

http://curator.apache.org/curator-recipes/path-cache.html

http://curator.apache.org/curator-recipes/shared-semaphore.html

http://curator.apache.org/curator-recipes/group-member.html

http://curator.apache.org/curator-recipes/leader-election.html

AKA delete

Add support (meaning: continuous integration testing) for OpenSUSE 42.3.

Add support (meaning: continuous integration testing) for Ubuntu 17.10.

client -> connection

http://curator.apache.org/curator-recipes/double-barrier.html

http://curator.apache.org/curator-recipes/persistent-ttl-node.html

Implement exceptions for the ZOO_ERRORS types.

How can a should new contributors add their features to the project and fix bugs? Through a CONTRIBUTING guide, of course!

http://curator.apache.org/curator-recipes/shared-reentrant-read-write-lock.html

Probably want to use Docker on TravisCI to run continuous integration.

http://curator.apache.org/curator-recipes/node-cache.html

Need a managed buffer type.

http://curator.apache.org/curator-recipes/barrier.html

http://curator.apache.org/curator-recipes/leader-latch.html

optional<T> is very helpful.

Need to build Debian packages from the Ubuntu builds.

http://curator.apache.org/curator-recipes/shared-counter.html

Need hook for a zk::future<T>.

http://curator.apache.org/curator-recipes/multi-shared-lock.html

This corresponds to the "sync" operation, which is called zoo_async to fit the naming pattern, is documented as "flush" because that's what the server does, but is actually a load fence on the client side.

These are required for ZK.