Apache Cassandra

The observable class keeps the list of std::function<void(Args...)> subscribers onboard. When set (called) the value notifies all observers about the change. Being void the callback that needs to start an asynchronous operation can do nothing but send it into the background by ignoring the top-most future. It would be nice if observable::operator() returned back a future. This would requir

Hey Crew,

Nice job on gocql, I'm a fan...

For my production services, I could use notification events (via callback or channel) when the gocql client disconnects and reconnects to/from Cassandra. This is useful for higher-level application logic (ie: invoke alarms, stop reading from a durable message queue, etc).

After looking through the code, it looks like the connection information is not p

In the starter class we System.out for "logging" since logback hasn't been enabled yet in this context. This is fine except it makes it a little difficult to grok for Starter related logs.

Add a helper method to prepend levels to the messages to make it easier to identify errors versus info.