-
Notifications
You must be signed in to change notification settings - Fork 208
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.
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
Using a go routine does not keep the connection alive #35
Comments
Ah, I think I understand now. The issue is that normally the state.Listener, which gets converted into a overseeerListener would block being closed, so the connection remains open. But if it is run in a go routine, that blocking doesn't happen. I wonder how to make that happen still. The issue is that I would like to be able to start up multiple listeners and have zero downtime restarts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using a go routine does not keep the connection alive.
If you do this same program without the go routine wrapper, the connection is not dropped.
The text was updated successfully, but these errors were encountered: