How to design proper release of a boost::asio socket or wrapper thereof

Question

I am making a few attempts at making my own simple asynch TCP server using boost::asio after not having touched it for several years.

The latest example listing I ca

Answer 1

The way that asio solves the "deletion problem" where there are outstanding async methods is that is splits each async-enabled object into 3 classes, eg:

• server
• server_service
• server_impl

there is one service per io_loop (see use_service<>). The service creates an impl for the server, which is now a handle class.

This has separated the lifetime of the handle and the lifetime of the implementation.

Now, in the handle's destructor, a message can be sent (via the service) to the impl to cancel all outstanding IO.

The handle's destructor is free to wait for those io calls to be queued if necessary (for example if the server's work is being delegated to a background io loop or thread pool).

It has become a habit with me to implement all io_service-enabled objects this way as it makes coding with aiso very much simpler.