Why does the socket close?

[kaihendry]

Shouldn't it stay open?

Running Chrome 43.0.2342.2

[skierkowski]

I'm assuming it's due to timeout, but I'll investigate.

[LarryKlugerDS]

I have the same question. Is a "keep-alive" needed?

This StackOverflow thread
http://stackoverflow.com/questions/9056159/websocket-closing-connection-automatically
seems to imply that there can be timeouts on both the browser and server side.

One of the answers suggesting catching the close event on the client and then automatically re-opening it.

Thoughts?
Thanks,
Larry

[skierkowski]

I'll have to dig into it more. I suspect it is on the client-side as I have other clients I've been testing (in Ruby) that didn't have any issues keeping alive out-of-the-box.