fix #119, panic gorilla ws when connection lost.

[ElecTwix]

fix #119
instead of panic it will return error when any send function call when connection lost.

[ElecTwix]

TLDR: This pull request aims to address issue #135 without requiring an additional function call.

[timpratim]

Hi @ElecTwix , thank you for the PR. Everything looks great. It would be great if we could add a test case for the Send method in the same PR. Happy to merge the PR then.

[ElecTwix]

It would be great if we could add a test case for the Send method in the same PR.

Hi @timpratim added test named connectionBreakAndClose for test the Send method to checks it's error return. I would like to add tests directly but it require mocks for gorilla itself for make it simpler I came up with this but in my next PRs, I will address this too.

[timpratim]

Thank you @ElecTwix. Appreciate it!
Merging the PR.

[hulkingshtick]

The function should exit on any error returned from ws.Conn.ReadMessage. You can fix by inlining WebSocket.read here and exiting when the call to ws.Conn.ReadMessage returns an error. Because handleError does not accurately detect all websocket errors, this thing can loop endlessly and eventually panic (the gorilla detects useless application loops).