TooTallNate/Java-WebSocket — pull request #52 by vijayraghunathan (2011-12-15 15:33:19+00:00)
Title: Don't set draft to null in releaseAndInitialize

Draft's don't have a setter in WebSocketClient, so setting them to null in this method makes this method pretty much pointless.

I'm not sure if it's necessary to call this before connect after an error (say, in case the server restarts) but it seems like if the function is there and public it should not leave the client in a state where it's unusable.