Maintain Connection with APRS-IS Server #123
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ter the timer is disposed without changing the timer period.
eddywine
approved these changes
Apr 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
As described in #122, the APRS-IS servers stop sending data after 48 hours, causing any connected client to stop receiving new packets.
This change adds an event that re-sends the login message every 6 hours to maintain connection and reset the 48hour timeout counter.
This resolves #122.
This uses
System.Threading.Timerinstead ofSystem.Timers.Timerto allow multi-threaded use of the underlyingTcpClientso that receiving is not interrupted.Changes
AprsIsConnectiondisposable, so the required changes were implemented for that as wellValidation