Update to make WebSocket++ work with modern Asio/Boost #1163
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.
Back in 2018, a bunch of Asio stuff was deprecated in Asio 1.12.0/Boost 1.66.0 to reflect the Networking TS. Now that it’s been a while, many of these deprecated functions and interfaces have been removed. As of Asio 1.34.0/Boost 1.87.0, WebSocket++ will not function. This commit makes the following changes and allows for functionality modern versions of Asio/Boost:
io_context
instead ofio_service
basic_waitable_timer::expiry
instead ofbasic_waitable_timer::expires_from_now
asio::post
instead ofio_context::post
executor_work_guard
instead ofio_context::work
resolver::resolve
directly instead of creatingresolver::query
resolver::results_type
instead ofresolver::iterator directly
max_listen_connextions
instead ofmax_connections
io_context::restart
instead ofio_context::reset
make_address
instead offrom_string