It's looking good. I left two comments on the commit.
Should we move to the Gorilla websocket library for the proxy-go instances as well? The GoDoc for the x/net websocket package suggests Gorilla since it is more actively maintained.
I had a look at this and my observations are the same as cohosh's in comment:5. Sending a CloseMessage before closing seems prudent as that's what the old code did.
Should we move to the Gorilla websocket library for the proxy-go instances as well?
Sure, IMO it's not as important because proxy-go only connects to a known server (not receiving connections from anywhere as the server does), and only needs to be compatible with the server's WebSocket implementation (unlike the server which has to be compatible with many browsers). It's a good idea anyway. I'd say let's get this ticket closed out first.
I had a look at this and my observations are the same as cohosh's in comment:5. Sending a CloseMessage before closing seems prudent as that's what the old code did.
Should we move to the Gorilla websocket library for the proxy-go instances as well?
Sure, IMO it's not as important because proxy-go only connects to a known server (not receiving connections from anywhere as the server does), and only needs to be compatible with the server's WebSocket implementation (unlike the server which has to be compatible with many browsers). It's a good idea anyway. I'd say let's get this ticket closed out first.