Refactor the way we close sockets into the RelaySubscriptionManager #1754
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issues covered
Follow up to #175
Description
This is some refactoring I did while debugging #175 that I stashed away at some point but now I'm submitting it. It basically moves our code for closing relay subscriptions from the
RelayService
into theRelaySubscriptionManager
. TheRelaySubscriptionManager
has progressively taken over more of... managing the subscriptions, and this is more of that. I also added more documentation and I think the lifecycle of opening a socket, starting a subscription, closing a subscription, and closing a socket, is easier to follow now that it's all happening in one file.How to test
Launch the app and look for relay problems. This could be rate limit errors in the console, or errors about "too many concurrent REQs", or it could look like content failing to load in the app.