Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why does the socket close? #5

Open
kaihendry opened this issue Mar 30, 2015 · 3 comments
Open

Why does the socket close? #5

kaihendry opened this issue Mar 30, 2015 · 3 comments

Comments

@kaihendry
Copy link

Shouldn't it stay open?

Running Chrome 43.0.2342.2
@skierkowski
Copy link
Member

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

@LarryKlugerDS
Copy link

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
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kaihendry @skierkowski @LarryKlugerDS