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.

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

Socket Disconnect when no remaining subscriptions #8

Merged
merged 3 commits into from
Mar 28, 2020

Conversation

lawmicha
Copy link
Contributor

Add a timeout to disconnect the websocket when there are no remaining subscriptions

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@lawmicha lawmicha requested review from royjit and wooj2 March 10, 2020 02:02
@lawmicha lawmicha changed the title Socket Disconnect based on remaining subscriptions Socket Disconnect when no remaining subscriptions Mar 10, 2020
@lawmicha lawmicha force-pushed the feature/socket-disconnect branch 2 times, most recently from ba30fc3 to a9c0391 Compare March 20, 2020 20:13
@lawmicha lawmicha force-pushed the feature/socket-disconnect branch from a9c0391 to 17c3b81 Compare March 20, 2020 20:15
guard let self = self else {
return
}
self.status = .notConnected
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldnt we check the number of connections here before sending disconnect to the websocket?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

woops, missed this after moving implemenentions back and forth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants