Compliance With Boost.Asio

Every asynchronous operation in Boost.Asio has associated characteristics that specify their behaviour.

An allocator determines how the asynchronous operations allocate memory resources.
A cancellation slot determines how the asynchronous operations support cancellation.
An executor determines the queuing and execution strategy for completion handlers.

This section expands further into the roles of allocators, cancellation slots, and executors, highlighting their integration and usage within the mqtt_client.

See Allocators for more information about how the mqtt_client supports and uses associated allocators.
See Per-Operation Cancellation for more information about how asynchronous operations within the mqtt_client support cancellation.
See Executors for more information about executors.