Boost.Asio VS asio

Indeed looks like it, strand_executor_service.hpp is using a Mutex internally (otherwise it wouldn't make sense to me).

as a side note, Asio is also released as an independent library without the boost stuff https://think-async.com/Asio/

Now that vinniefalco is going to kill off the asio standalone (see deprecate standalone ) and only support boost what would people then recommend to switch over to.

The ASIO framework can be found at https://think-async.com/Asio/ and the relevant license for its use is included in the GitHub repository in the Vendor/licenses directory.

The library is found at https://think-async.com/Asio/.

Asio Extracted from the much bigger Boost C++ library, it's apparently a really good networking library. As a bonus it also handles async / threads. Here's a really good video tutorial by OneLoneCoder

Yes: https://github.com/chriskohlhoff/asio/blob/master/asio/include/asio/coroutine.hpp

Here's the main contributor to Asio. I looked at Asio's repository and this was the first guy.

On mobile so have trouble finding relevant docs, but this commit seems to contain bulk of the io_uring support: https://github.com/boostorg/asio/commit/292dcdcb94d1e5cd47b3275c1e8ad93dd19dc912

I guess this file will have the answer: https://github.com/boostorg/asio/blob/develop/include/boost/asio/impl/read_until.hpp

For example, the authour of Boost.Asio demonstrated setting up SSL protocol here. He provides ca.pem and sha1.0 files, yet does not load sha1.0 in client.cpp.

Doing some research on other people's experience in implementing custom stream buffers, I rarely see seekoff (and it's companion seekpos) being overriden. Boost ASIO's basic_streambuf does not. This article on writing custom stream buffers and this other article (both show up on the first page in a Google search) do not.