Switch from epee http client to boost::beast. All HTTP now non-blocking. #150
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
vtnerd
force-pushed
the
feature/beast_client_squashed
branch
from
02b25a2
to
359ebcd
Compare
|
Forgot to include new files. Force pushed a change with them. |
vtnerd
force-pushed
the
feature/beast_client_squashed
branch
from
359ebcd
to
dae3c6d
Compare
|
Force push some missing includes fixes. |
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.
As the title suggests, this removes all blocking epee HTTP client code and moves to an async
boost::beastimplementation. The REST endpoint/loginis now always non-blocking, even with account creation webhooks. The scanner no longer blocks for webhooks, and instead queues up requests. The rate exchange fetch code is also now async.