boost-asio-pro

Topics in the source

• Boost.Asio / standalone Asio
• Overview
• Step 1: pick the style (do this before writing code)
• Step 2: version floors (verified by compiling, not from docs)
• Step 3: the rules that are actually easy to get wrong
• Anti-Patterns
• Boost.Asio vs standalone Asio
• Before you call it done

Write async C++ networking code that compiles on the user's Boost, not the newest one. Asio's API changed shape three times (classic ioservice → iocontext → C++20 coroutines) and most Asio code on the internet is from the first era, so pick the style from the toolchain first, then follow that style's reference file. References: Boost.Asio · standalone Asio Use this skill whenever async C++ networking code is being written or reviewed — and especially when the target toolchain is old, where coroutine examples simply will not compile. The three worked implementations it references are CI-verified from Boost 1.62 (2016) through 1.90. Determine the Boost (or Asio) version and the C++ standard actually in use — findpackage(Boost) output, dpkg -l libboost-dev, brew info boost, CMAKECXXSTANDARD, or ask. Do not assume the newest. | Boost | C++ std | Style | Read | |-------|---------|-------|------| | ≥ 1.77 | C++20 | Coroutines (coawait + awaitable ) — preferred | references/coroutines.md | | ≥ 1.74 | C++11–17 | Completion handlers (callbacks) — the portable baseline | references/pre-cpp20.md | | ≥ 1.80 | C++11–17 | Stackful asio::spawn + yieldcontext (links Boost.Coroutine — not header-on

This is an excerpt. Refer to the complete source and its current requirements.