boundary/ordasity — pull request #15 by jdanbrown (2012-08-16 23:52:28+00:00)
Title: Fix: Don't assume the zk client hasn't yet connected

If the user supplies their own zk client to cluster.join (or cluster.connect), and their zk client has already established a session, then the cluster will register a watch for a SyncConnected event but never receive one, since it has already fired long ago, before the cluster started listening.

This bug was introduced in my earlier #13, which was a simple change that quietly violated the assumption that the cluster's zk client would trigger a SyncConnected after cluster.join.

This fix depends on (and includes) #14.