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

The publisher should close the Ably connection when it has no trackables #170

Closed
KacperKluka opened this issue Feb 8, 2021 · 1 comment · Fixed by #778
Closed

The publisher should close the Ably connection when it has no trackables #170

KacperKluka opened this issue Feb 8, 2021 · 1 comment · Fixed by #778
Assignees
Labels
bug Something isn't working. It's clear that this does need to be fixed. enhancement New feature or improved functionality.

Comments

@KacperKluka
Copy link
Contributor

KacperKluka commented Feb 8, 2021

When there are no trackables in the publisher then the Ably connection should be closed.

We can use the ably.close() and ably.connect() methods to accomplish that.

@KacperKluka
Copy link
Contributor Author

Closing and reopening the connection isn't a big problem itself. The real issue is that due to the fact that the Ably wrapper isn't very safe in terms of multithreading, with current implementation we might end up in a state where the connection is closed and it won't be reopened. Therefore, we should wait for #440 to be resolved before working on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. It's clear that this does need to be fixed. enhancement New feature or improved functionality.
2 participants