Re: [boost] singleton asio::demuxer as default? (was: asioformalreview begins)

Arkadiy Vertleyb wrote:

That should not be difficult to achieve with derivation or some sort of policy. Looks like async_socket might be derived from sync_socket (or contain it).

This was also my thought - public derivation. I.e., the current socket class is refactored into two classes - base (sync_socket) and and derived (async_socket). The sync_socket class won't know anyhing about demuxers (it doesn't need to). The async_socket class will add asynchronous operations and binding to a specific demuxer. Chris, what do you think about this?