README.markdown in zk-1.6.3 vs README.markdown in zk-1.6.4
- old
+ new
@@ -63,9 +63,14 @@
[Mongoid]: http://mongoid.org/
[EventMachine]: https://github.com/eventmachine/eventmachine
[zk-eventmachine]: https://github.com/slyphon/zk-eventmachine
## NEWS ##
+### v1.6.4 ###
+
+* Remove unnecessary dependency on backports gem
+* *Fix for use in resque!* A small bug was preventing resque from activating the fork hook.
+
### v1.6.2 ###
* Change state call to reduce the chances of deadlocks
One of the problems I've been seeing is that during some kind of shutdown event, some method will call `closed?` or `connected?` which will acquire a mutex and make a call on the underlying connection at the *exact* moment necessary to cause a deadlock. In order to help prevent this, and building on some changes from 1.5.3, we now treat our cached `@last_cnx_state` as the current state of the connection and don't touch the underlying connection object (except in the case of the java driver, which is safe).