Add HCWebSocketSetPingInterval #867
Open
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
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.
Not all platforms behave similarly or have similar capabilities but this is a best effort to at least expose some control over the ping behavior by adding HCWebSocketSetPingInterval and HCWebSocketGetPingInterval. If the client did not specify a ping interval the library behaves as before to avoid unexpected changes.
If the client does, Android and websocketpp now have a pong-timeout to help detect broken connections. Unfortunately, WinRT does not have any options for ping/pong frames and WinHttp can (as far as I could tell) only send unsolicited pongs.