{"id":883,"date":"2023-01-05T23:25:13","date_gmt":"2023-01-05T15:25:13","guid":{"rendered":"https:\/\/www.fanyamin.com\/wordpress\/?p=883"},"modified":"2023-01-05T23:25:13","modified_gmt":"2023-01-05T15:25:13","slug":"boost-asio-note-executors","status":"publish","type":"post","link":"https:\/\/www.fanyamin.com\/wordpress\/?p=883","title":{"rendered":"boost asio note – Executors"},"content":{"rendered":"
\n

Every asynchronous agent has an associated executor. An agent's executor determines how the agent's completion handlers are queued and ultimately run.<\/p>\n<\/blockquote>\n

\u6bcf\u4e2a\u5f02\u6b65\u4ee3\u7406\u90fd\u6709\u4e00\u4e2a\u5173\u8054\u7684\u6267\u884c\u5668\u3002 \u4ee3\u7406\u7684\u6267\u884c\u8005\u786e\u5b9a\u4ee3\u7406\u7684\u5b8c\u6210\u5904\u7406\u7a0b\u5e8f\u5982\u4f55\u6392\u961f\u5e76\u6700\u7ec8\u8fd0\u884c<\/p>\n

\n

Example uses of executors include:<\/p>\n

Coordinating a group of asynchronous agents that operate on shared data structures, ensuring that the agents' completion handlers never run concurrently[5].
\nEnsuring that agents are run on specified execution resource (e.g. a CPU) that is proximal to data or an event source (e.g. a NIC).
\nDenoting a group of related agents, and so enabling dynamic thread pools to make smarter scheduling decisions (such as moving the agents between execution resources as a unit).
\nQueuing all completion handlers to run on a GUI application thread, so that they may safely update user interface elements.
\nReturning an asynchronous operation's default executor as-is, to run completion handlers as close as possible to the event that triggered the operation's completion.
\nAdapting an asynchronous operation's default executor, to run code before and after every completion handler, such as logging, user authorisation, or exception handling.
\nSpecifying a priority for an asynchronous agent and its completion handlers.<\/p>\n<\/blockquote>\n

\u6267\u884c\u8005\u7684\u793a\u4f8b\u7528\u9014\u5305\u62ec\uff1a<\/p>\n