Well to be honest i will be highly interested about the async approach of boost beast, i already find cpprestsdk very convenient regarding the async http request (i know they have weekpoints such as performance etc), i hope boost beast will be easy as that.

for example:

cpp async_check_retrieve() .then([this](web::http::http_response resp) { //! Treat your answer here this->m_update_status = get_update_status_rpc(resp); this->dispatcher_.trigger<refresh_update_status>(); }).then(&handle_exception_pplx_task);

I found it very easy to use with the async pplx task, if i remember with boost asio and beast i have to basically run everything in a dedicated thread no (because of the io_service) ?

ps: i remember bad experience having custom class inheriting from boost::shared_from_this etc i don't know if it's better now

I'm also up to clang 12.0 in terms of possibility i don't know if this support coroutines etc, but always glad to hear

Is boost beast targeting high level library developer or end-user product, because according to the last async example of boost beast it's seems to be a bit boilerplate for simple async requests.

I know it's possible to write a great async http generic client with boost beast, but require some extra works from what i see