Websocket Async Client as a DLL about beast HOT 1 CLOSED

The problem is that you are treating async operations as if they finish immediately. You need to have a mechanism to wait for operations until they complete.

It is not clear how your code benefits from asynchronous operations, maybe you just need to use synchronous API. You can also use asio::use_future completion token to wait for operations. you can find an example here: https://github.com/boostorg/asio/blob/develop/example/cpp11/futures/daytime_client.cpp

Generally speaking, asynchronous applications should be built around an executor (such as asio::any_io_executor) to efficiently and easily wait for asynchronous operations. Otherwise, scaling an application would become very difficult, requiring explicit synchronization mechanisms that make the code error-prone.

from beast.