@eric and I are now even
This is the basis for the Locker's blocking behavior. Now that this has been implemented, we can add support in the various Lockers for passing this value through.
will help with calling lock.assert! when using zk.with_lock()
…nnection Instead of calling methods on the underlying connection (which may be in the process of closing or in some hung state), use @last_cnx_state which is the value of the last seen session event. This means that we're only 'connected' after we've seen the event, however this is really not that much different in practice. This should prevent many deadlocks, as we're not calling down into the C layer in an indeterminate state.
… to 1.6.1