Disconnect handler is never called

[Dids]

From what I've been able to gather, the disconnect handler is never getting called, and I'm assuming because there's no actual reconnecting support, the connection will basically end up in a "bad state", where it thinks it's still connected.

[tomkcook]

I'm seeing this too. On disconnect, usually the first sign is that the call to ReadMessage() at line gowebsocket.go:131 exits with an error. The only effect this has is that a message is logged and the enclosing goroutine exits, but whatever called Connect() is never informed.

Pull request #6 addresses this.

[tomkcook]

My pull request works in the case where the connection is actively interrupted (eg the computer's ethernet cable is yanked or the wifi connection drops out). It doesn't address the case where the network is interrupted further upstream, because the library implements no timeouts / deadlines. I'll work up a pull request to address this.

[jesst3r]

still not working?