add quick-n-dirty ready state check
fix IDENTIFY race: use "close" instead of "error" for reconnection

almost seems like a node behaviour issue, but there are some cases when the socket will
emit multiple errors, so this screws with the Connection state
Release 0.5.1