Update to use boost::beast (websocket transition). Needs testing #4
Conversation
This file contains hidden or 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.
This includes changes in the #3 lookahead PR.
This transitions the http client to
boost::beastsuch that the REST calls run asynchronously in aboost::asioevent loop. The objective is to introduce a "push" (websocket) interface from the server, such that polling is no longer needed on the frontend. This should reduce server overload, but add some complexity on both ends. The code will automatically fall back onto a polling scheme if the server doesn't support the new websocket mode.I'm leaving this as draft until the lookahead patch gets finalized; fcmp++ spending is a higher priority.