Basic Boost.Asio Anatomy
Boost.Asio may be used to perform both synchronous and asynchronous operations on I/O objects such as sockets. Before using Boost.Asio it may be useful to get a conceptual picture of the various parts of Boost.Asio, your program, and how they work together.
As an introductory example, let's consider what happens when you perform a connect operation on a socket. We shall start by examining synchronous operations.
Your program will have at least one I/O execution context, such as an boost::asio::io_context object, boost::asio::thread_pool object, or boost::asio::system_context. This I/O execution context represents your program's link to the operating system's I/O services.
boost::asio::io_context io_context;
To perform I/O operations your program will need an I/O object such as a TCP socket:
boost::asio::ip::tcp::socket socket(io_context);
When a synchronous connect operation is performed, the following sequence of events occurs:
- Your program initiates the connect operation by calling the I/O object:
socket.connect(server_endpoint);
The I/O object forwards the request to the I/O execution context.
The I/O execution context calls on the operating system to perform the connect operation.
The operating system returns the result of the operation to the I/O execution context.
The I/O execution context translates any error resulting from the operation into an object of type boost::system::error_code. An error_code may be compared with specific values, or tested as a boolean (where a false result means that no error occurred). The result is then forwarded back up to the I/O object.
The I/O object throws an exception of type boost::system::system_error if the operation failed. If the code to initiate the operation had instead been written as:
boost::system::error_code ec;
socket.connect(server_endpoint, ec);
then the error_code variable ec would be set to the result of the operation, and no exception would be thrown.
// 下面是異步操作時的事件(event)發(fā)生順序
When an asynchronous operation is used, a different sequence of events occurs.
// 第一步是使用async_connect初始化連接，同時按照異步操作完成返回時的需要創(chuàng)建你自己的回調(diào)處理函數(shù)handler
- Your program initiates the connect operation by calling the I/O object:
socket.async_connect(server_endpoint, your_completion_handler);
where your_completion_handler is a function or function object with the signature:
void your_completion_handler(const boost::system::error_code& ec);
The exact signature required depends on the asynchronous operation being performed. The reference documentation indicates the appropriate form for each operation.
// I/O object會將請求轉(zhuǎn)發(fā)給 I/O execution context
- The I/O object forwards the request to the I/O execution context.
// I/O execution context 會通知OS(操作系統(tǒng))開始一次異步的連接
- The I/O execution context signals to the operating system that it should start an asynchronous connect.
Time passes. (In the synchronous case this wait would have been contained entirely within the duration of the connect operation.)
// 當(dāng)OS系統(tǒng)層面的操作完成時，結(jié)果會被放入一個queue， I/O execution contex可以將其讀取
- The operating system indicates that the connect operation has completed by placing the result on a queue, ready to be picked up by the I/O execution context.
// 如果使用 io_context 作為 I/O execution contex ，要想這個結(jié)果被io_context檢索到，則需要手動執(zhí)行 io_context::run() 或類似的方法。 在執(zhí)行 io_context::run() 的時候如果有未完成的異步操作，則run會被阻塞，所以需要在你的第一個異步操作開始后立即執(zhí)行io_context::run()
- When using an io_context as the I/O execution context, your program must make a call to io_context::run() (or to one of the similar io_context member functions) in order for the result to be retrieved. A call to io_context::run() blocks while there are unfinished asynchronous operations, so you would typically call it as soon as you have started your first asynchronous operation.
//在run內(nèi)部，I/O execution context(通常也是io_context)將操作結(jié)果出隊，然后轉(zhuǎn)換成error_code，最后傳遞給你的程序設(shè)置好的handler
- While inside the call to io_context::run(), the I/O execution context dequeues the result of the operation, translates it into an error_code, and then passes it to your completion handler.
This is a simplified picture of how Boost.Asio operates. You will want to delve further into the documentation if your needs are more advanced, such as extending Boost.Asio to perform other types of asynchronous operations.
Reference:
