El 15/08/2025 a las 23:55, Vinnie Falco via Boost escribió:
On Fri, Aug 15, 2025 at 1:41 PM Vinícius dos Santos Oliveira < vini.ipsmaker@gmail.com> wrote:
If it's going to be a new library with a new design, it should go through the Boost peer review process.
Yes to the review process, which is why I am first gauging interest.
As for the "new design," I am not looking to innovate here. The fork would use the same interface principles as Asio and the same code, except for things that we want to modernize which would not be accepted in original Asio. The canonical example being the use of `std::error_code`. Where we would differ is that there could be support for things that Asio won't do, such as native Botan support for TLS. Or this WolfSSL which is alluded to in the neglected GitHub issue in the OP.
I don't know if your idea is going to be sufficiently different to warrant
a new library that's mostly going to be an overlap of what Boost.Asio already does though.
I'm not sure it needs to be sufficiently different, other than having responsive developers and active support. This is why I am posting to the mailing list. Would a fork of Asio which keeps mostly the same interface, has enhancements desired by the community, and has updated documentation and ongoing support worth having as a Boost library?
Hi, Which is the plan to maintain the new features that Asio will get over time? I've not followed Asio evolution, but I guess more features are being added in newer versions (there are some experimental features mentioned in the library documentation). Having support for other SSL libraries (MbedTLS also comes to my mind) is a nice feature. Reducing dependencies to the minimum is also a good feature, although I've seen that the weight of the library has been considerably reduced in the latest Boost releases. If understand the proposal correctly, if the fork passes the review, then we would have 2 networking libraries inside Boost (Boost.Asio + Boost.ForkedAsio)? Best, Ion PS: Building "great things" above a networking library also includes something like Boost.Curl, the C++ swiss army knife for internet protocols?