1562 strings

Translation Key Source string Target string
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
HTTP, fast (optimized for speed)
HTTP, fast (optimized for speed)
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/http/server/fast/http_server_fast.cpp http_server_fast.cpp]
[path_link example/http/server/fast/http_server_fast.cpp http_server_fast.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
HTTP, small (optimized for space)
HTTP, small (optimized for space)
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/http/server/small/http_server_small.cpp http_server_small.cpp]
[path_link example/http/server/small/http_server_small.cpp http_server_small.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
HTTP, flex (plain + SSL)
HTTP, flex (plain + SSL)
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/http/server/flex/http_server_flex.cpp http_server_flex.cpp]
[path_link example/http/server/flex/http_server_flex.cpp http_server_flex.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
These WebSocket servers echo back any message received, keeping the session open until the client disconnects. All asynchronous servers support timeouts.
These WebSocket servers echo back any message received, keeping the session open until the client disconnects. All asynchronous servers support timeouts.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
152
WebSocket, synchronous
WebSocket, synchronous
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/sync/websocket_server_sync.cpp websocket_server_sync.cpp]
[path_link example/websocket/server/sync/websocket_server_sync.cpp websocket_server_sync.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/sync-ssl/websocket_server_sync_ssl.cpp websocket_server_sync_ssl.cpp]
[path_link example/websocket/server/sync-ssl/websocket_server_sync_ssl.cpp websocket_server_sync_ssl.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
152
WebSocket, asynchronous
WebSocket, asynchronous
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/async/websocket_server_async.cpp websocket_server_async.cpp]
[path_link example/websocket/server/async/websocket_server_async.cpp websocket_server_async.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/async-ssl/websocket_server_async_ssl.cpp websocket_server_async_ssl.cpp]
[path_link example/websocket/server/async-ssl/websocket_server_async_ssl.cpp websocket_server_async_ssl.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
152
WebSocket, asynchronous Unix domain sockets
WebSocket, asynchronous Unix domain sockets
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/async-local/websocket_server_async_local.cpp websocket_server_async_local.cpp]
[path_link example/websocket/server/async-local/websocket_server_async_local.cpp websocket_server_async_local.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
152
WebSocket, coroutine
WebSocket, coroutine
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/coro/websocket_server_coro.cpp websocket_server_coro.cpp]
[path_link example/websocket/server/coro/websocket_server_coro.cpp websocket_server_coro.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/coro-ssl/websocket_server_coro_ssl.cpp websocket_server_coro_ssl.cpp]
[path_link example/websocket/server/coro-ssl/websocket_server_coro_ssl.cpp websocket_server_coro_ssl.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
WebSocket, stackless coroutine
WebSocket, stackless coroutine
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/stackless/websocket_server_stackless.cpp websocket_server_stackless.cpp]
[path_link example/websocket/server/stackless/websocket_server_stackless.cpp websocket_server_stackless.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/stackless-ssl/websocket_server_stackless_ssl.cpp websocket_server_stackless_ssl.cpp]
[path_link example/websocket/server/stackless-ssl/websocket_server_stackless_ssl.cpp websocket_server_stackless_ssl.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
WebSocket, C++ 20 coroutine
WebSocket, C++ 20 coroutine
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/awaitable/websocket_server_awaitable.cpp websocket_server_awaitable.cpp]
[path_link example/websocket/server/awaitable/websocket_server_awaitable.cpp websocket_server_awaitable.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
WebSocket, fast (suited for benchmarks)
WebSocket, fast (suited for benchmarks)
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/fast/websocket_server_fast.cpp websocket_server_fast.cpp]
[path_link example/websocket/server/fast/websocket_server_fast.cpp websocket_server_fast.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
Servers (Advanced)
Servers (Advanced)
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
These servers offer both HTTP and WebSocket services on the same port, and illustrate the implementation of advanced features.
These servers offer both HTTP and WebSocket services on the same port, and illustrate the implementation of advanced features.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
Advanced
Advanced
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[itemized_list [Timeouts] [Multi-threaded] [HTTP pipelining] [Parser-oriented HTTP reading] [Dual protocols: HTTP and WebSocket] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] ]
[itemized_list [Timeouts] [Multi-threaded] [HTTP pipelining] [Parser-oriented HTTP reading] [Dual protocols: HTTP and WebSocket] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] ]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/advanced/server/advanced_server.cpp advanced_server.cpp]
[path_link example/advanced/server/advanced_server.cpp advanced_server.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
Advanced, flex (plain + SSL)
Advanced, flex (plain + SSL)
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[itemized_list [Timeouts] [Multi-threaded] [HTTP pipelining] [Parser-oriented HTTP reading] [Dual protocols: HTTP and WebSocket] [Flexible ports: plain and SSL on the same port] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] ]
[itemized_list [Timeouts] [Multi-threaded] [HTTP pipelining] [Parser-oriented HTTP reading] [Dual protocols: HTTP and WebSocket] [Flexible ports: plain and SSL on the same port] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] ]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/advanced/server-flex/advanced_server_flex.cpp advanced_server_flex.cpp]
[path_link example/advanced/server-flex/advanced_server_flex.cpp advanced_server_flex.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
Advanced, flex (plain + SSL) with awaitable
Advanced, flex (plain + SSL) with awaitable
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[itemized_list [Timeouts] [Multi-threaded] [HTTP pipelining] [Parser-oriented HTTP reading] [Dual protocols: HTTP and WebSocket] [Flexible ports: plain and SSL on the same port] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] [Usage of cancellation_signals] ]
[itemized_list [Timeouts] [Multi-threaded] [HTTP pipelining] [Parser-oriented HTTP reading] [Dual protocols: HTTP and WebSocket] [Flexible ports: plain and SSL on the same port] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] [Usage of cancellation_signals] ]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/advanced/server-flex-awaitable/advanced_server_flex_awaitable.cpp advanced_server_flex_awaitable.cpp]
[path_link example/advanced/server-flex-awaitable/advanced_server_flex_awaitable.cpp advanced_server_flex_awaitable.cpp]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
Chat Server, multi-threaded
Chat Server, multi-threaded
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[itemized_list [Multi-threaded] [Broadcasting Messages] [Multi-user Chat Server] [JavaScript Browser Client] [Parser-oriented HTTP reading] [Dual protocols: HTTP and WebSocket] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] ]
[itemized_list [Multi-threaded] [Broadcasting Messages] [Multi-user Chat Server] [JavaScript Browser Client] [Parser-oriented HTTP reading] [Dual protocols: HTTP and WebSocket] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] ]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
193
[path_link example/websocket/server/chat-multi chat-multi]
[path_link example/websocket/server/chat-multi chat-multi]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
This example demonstrates a websocket chat server, allowing multiple users to connect and participate in live, group messaging. It comes with a tiny front end implemented in JavaScript and HTML5 which runs in any browser. The example is accompanied by a one hour presentation which provides a discussion of networking concepts, followed by in-depth explanation of how the client and server are constructed. This talk was delivered at [@https://cppcon.org CppCon 2018]. The source code in the Beast example contains improvements to the original program.
This example demonstrates a websocket chat server, allowing multiple users to connect and participate in live, group messaging. It comes with a tiny front end implemented in JavaScript and HTML5 which runs in any browser. The example is accompanied by a one hour presentation which provides a discussion of networking concepts, followed by in-depth explanation of how the client and server are constructed. This talk was delivered at [@https://cppcon.org CppCon 2018]. The source code in the Beast example contains improvements to the original program.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
Chat WebSocket Server and JavaScript Client
Chat WebSocket Server and JavaScript Client
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
Features
Features
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
Sources
Sources
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[itemized_list [C++] [Timeouts] [Multi-threaded] [Broadcast to multiple peers] [Dual protocols: HTTP and WebSocket] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] ]
[itemized_list [C++] [Timeouts] [Multi-threaded] [Broadcast to multiple peers] [Dual protocols: HTTP and WebSocket] [Clean exit via SIGINT (CTRL+C) or SIGTERM (kill)] ]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
260
[path_link example/websocket/server/chat-multi chat-multi]
[path_link example/websocket/server/chat-multi chat-multi]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[itemized_list [JavaScript / HTML5] [Runs in the browser] [Delivered by the server] [Only 60 lines total including UI] [Completely portable graphics] ]
[itemized_list [JavaScript / HTML5] [Runs in the browser] [Delivered by the server] [Only 60 lines total including UI] [Completely portable graphics] ]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 02 Examples / Examples (qbk) — Chinese (Simplified Han script)
[path_link example/websocket/server/chat-multi/chat_client.html chat_client.html]
[path_link example/websocket/server/chat-multi/chat_client.html chat_client.html]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
Networking
Networking
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
This library uses the [@http://cplusplus.github.io/networking-ts/draft.pdf Networking Technical Specification], scheduled to become an official part of C++ no sooner than the year 2023. Three implementations exist, with cosmetic differences but otherwise using the same function signatures and type declarations: Boost.Asio, stand-alone Asio, and networking-ts-impl. This table shows how a variable of type `io_context` is declared in each implementation by including the appropriate header and using a suitable namespace alias:
This library uses the [@http://cplusplus.github.io/networking-ts/draft.pdf Networking Technical Specification], scheduled to become an official part of C++ no sooner than the year 2023. Three implementations exist, with cosmetic differences but otherwise using the same function signatures and type declarations: Boost.Asio, stand-alone Asio, and networking-ts-impl. This table shows how a variable of type `io_context` is declared in each implementation by including the appropriate header and using a suitable namespace alias:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
Networking Implementations
Networking Implementations
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
Namespace and Header Example
Namespace and Header Example
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
__Asio__
__Asio__
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
#include <boost/asio/io_context.hpp>
namespace net = boost::asio;
net::io_context ioc;
#include <boost/asio/io_context.hpp>
namespace net = boost::asio;
net::io_context ioc;
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
[@https://think-async.com/Asio/ Asio (Standalone)]
[@https://think-async.com/Asio/ Asio (Standalone)]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
#include <asio/io_context.hpp>
namespace net = asio;
net::io_context ioc;
#include <asio/io_context.hpp>
namespace net = asio;
net::io_context ioc;
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
[@https://github.com/chriskohlhoff/networking-ts-impl networking-ts-impl]
[@https://github.com/chriskohlhoff/networking-ts-impl networking-ts-impl]
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
#include <experimental/io_context>
namespace net = std::experimental::net;
net::io_context ioc;
#include <experimental/io_context>
namespace net = std::experimental::net;
net::io_context ioc;
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
This document refers to the three implementations above interchangeably and collectively as [*Networking] (or just ['networking]). The Boost.Asio and Asio flavors of Networking provide additional features not currently proposed for C++, but likely to appear in a future specification, such as:
This document refers to the three implementations above interchangeably and collectively as [*Networking] (or just ['networking]). The Boost.Asio and Asio flavors of Networking provide additional features not currently proposed for C++, but likely to appear in a future specification, such as:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
* [@boost:/doc/html/boost_asio/reference/serial_port.html Serial ports]
* [@boost:/doc/html/boost_asio/reference/local__stream_protocol.html UNIX domain sockets]
* [@boost:/doc/html/boost_asio/reference/signal_set.html POSIX signals] (e.g. SIGINT, SIGABORT)
* [@boost:/doc/html/boost_asio/reference/ssl__stream.html TLS streams] (such as OpenSSL)
* [@boost:/doc/html/boost_asio/reference/serial_port.html Serial ports]
* [@boost:/doc/html/boost_asio/reference/local__stream_protocol.html UNIX domain sockets]
* [@boost:/doc/html/boost_asio/reference/signal_set.html POSIX signals] (e.g. SIGINT, SIGABORT)
* [@boost:/doc/html/boost_asio/reference/ssl__stream.html TLS streams] (such as OpenSSL)
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
Boost.Beast depends specifically on the Boost.Asio flavor of Networking, although this may change in the future. While this library offers performant implementations of the HTTP and WebSocket network protocols, it depends on the networking interfaces to perform general tasks such as performing domain name resolution (DNS lookup), establishing outgoing connections, and accepting incoming connections. Callers are responsible for interacting with networking to initialize objects to the correct state where they are usable by this library.
Boost.Beast depends specifically on the Boost.Asio flavor of Networking, although this may change in the future. While this library offers performant implementations of the HTTP and WebSocket network protocols, it depends on the networking interfaces to perform general tasks such as performing domain name resolution (DNS lookup), establishing outgoing connections, and accepting incoming connections. Callers are responsible for interacting with networking to initialize objects to the correct state where they are usable by this library.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
In this documentation, the example code, and the implementation, the `net` namespace is used to qualify Networking identifiers. For Boost.Beast, `net` will be an alias for the `boost::asio` namespace.
In this documentation, the example code, and the implementation, the `net` namespace is used to qualify Networking identifiers. For Boost.Beast, `net` will be an alias for the `boost::asio` namespace.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
To further ease of use, this library provides an extensive collection of types and algorithms. This section of the documentation explains these types and algorithms, provides examples of usage, and also provides refreshers and tutorials for working with networking.
To further ease of use, this library provides an extensive collection of types and algorithms. This section of the documentation explains these types and algorithms, provides examples of usage, and also provides refreshers and tutorials for working with networking.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
Abbreviations
Abbreviations
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / Core (qbk) — Chinese (Simplified Han script)
This documentation assumes familiarity with __Asio__, which is required to work with Beast. Sample code and identifiers used throughout are written as if the following declarations are in effect:
This documentation assumes familiarity with __Asio__, which is required to work with Beast. Sample code and identifiers used throughout are written as if the following declarations are in effect:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
To use Beast effectively, a prior understanding of Networking is required. This section reviews these concepts as a reminder and guide for further learning.
To use Beast effectively, a prior understanding of Networking is required. This section reviews these concepts as a reminder and guide for further learning.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
A [@https://en.wikipedia.org/wiki/Computer_network ['network]] allows programs located anywhere to exchange information after opting-in to communications by establishing a [@https://en.wikipedia.org/wiki/Data_link ['connection]]. Data may be reliably transferred across a connection in both directions ([@https://en.wikipedia.org/wiki/Duplex_(telecommunications) ['full-duplex]]) with bytes arriving in the same order they were sent. These connections, along with the objects and types used to represent them, are collectively termed [link beast.concepts.streams ['streams]]. The computer or device attached to the network is called a [@https://en.wikipedia.org/wiki/Host_(network) ['host]], and the program on the other end of an established connection is called a [@https://en.wikipedia.org/wiki/Peer-to-peer ['peer]].
A [@https://en.wikipedia.org/wiki/Computer_network ['network]] allows programs located anywhere to exchange information after opting-in to communications by establishing a [@https://en.wikipedia.org/wiki/Data_link ['connection]]. Data may be reliably transferred across a connection in both directions ([@https://en.wikipedia.org/wiki/Duplex_(telecommunications) ['full-duplex]]) with bytes arriving in the same order they were sent. These connections, along with the objects and types used to represent them, are collectively termed [link beast.concepts.streams ['streams]]. The computer or device attached to the network is called a [@https://en.wikipedia.org/wiki/Host_(network) ['host]], and the program on the other end of an established connection is called a [@https://en.wikipedia.org/wiki/Peer-to-peer ['peer]].
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The [@https://en.wikipedia.org/wiki/Internet ['internet]] is a global network of interconnected computers that use a variety of standardized communication protocols to exchange information. The most popular protocol is [@https://en.wikipedia.org/wiki/Transmission_Control_Protocol ['TCP/IP]], which this library relies on exclusively. The protocol takes care of the low level details so that applications see a ['stream], which is the reliable, full-duplex connection carrying the ordered set of bytes described above. A [@https://en.wikipedia.org/wiki/Server_(computing) ['server]] is a powerful, always-on host at a well-known network name or network address which provides data services. A [@https://en.wikipedia.org/wiki/Client_(computing) ['client]] is a transient peer which connects to a server to exchange data, and goes offline.
The [@https://en.wikipedia.org/wiki/Internet ['internet]] is a global network of interconnected computers that use a variety of standardized communication protocols to exchange information. The most popular protocol is [@https://en.wikipedia.org/wiki/Transmission_Control_Protocol ['TCP/IP]], which this library relies on exclusively. The protocol takes care of the low level details so that applications see a ['stream], which is the reliable, full-duplex connection carrying the ordered set of bytes described above. A [@https://en.wikipedia.org/wiki/Server_(computing) ['server]] is a powerful, always-on host at a well-known network name or network address which provides data services. A [@https://en.wikipedia.org/wiki/Client_(computing) ['client]] is a transient peer which connects to a server to exchange data, and goes offline.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
A vendor supplies a program called a [@https://en.wikipedia.org/wiki/Device_driver ['device driver]], enabling networking hardware such as an [@https://en.wikipedia.org/wiki/Network_interface_controller ['ethernet adaptor]] to talk to the operating system. This in turn permits running programs to interact with networking using various flavors of interfaces such as [@https://en.wikipedia.org/wiki/Berkeley_sockets ['Berkeley sockets]] or [@https://en.wikipedia.org/wiki/Winsock ['Windows Sockets 2]] ("Winsock").
A vendor supplies a program called a [@https://en.wikipedia.org/wiki/Device_driver ['device driver]], enabling networking hardware such as an [@https://en.wikipedia.org/wiki/Network_interface_controller ['ethernet adaptor]] to talk to the operating system. This in turn permits running programs to interact with networking using various flavors of interfaces such as [@https://en.wikipedia.org/wiki/Berkeley_sockets ['Berkeley sockets]] or [@https://en.wikipedia.org/wiki/Winsock ['Windows Sockets 2]] ("Winsock").
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Networking in C++, represented by __Asio__, [@https://think-async.com/Asio/ Asio], and __NetTS__, provides a layer of abstraction to interact portably with the operating system facilities for not just networking but general [@https://en.wikipedia.org/wiki/Input/output ['input/output]] ("I/O").
Networking in C++, represented by __Asio__, [@https://think-async.com/Asio/ Asio], and __NetTS__, provides a layer of abstraction to interact portably with the operating system facilities for not just networking but general [@https://en.wikipedia.org/wiki/Input/output ['input/output]] ("I/O").
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Buffers
Buffers
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
A [@https://en.wikipedia.org/wiki/Data_buffer ['buffer]] holds a contiguous sequence of bytes used when performing I/O. The types [@boost:/doc/html/boost_asio/reference/const_buffer.html `net::const_buffer`] and [@boost:/doc/html/boost_asio/reference/mutable_buffer.html `net::mutable_buffer`] represent these memory regions as type-safe pointer/size pairs:
A [@https://en.wikipedia.org/wiki/Data_buffer ['buffer]] holds a contiguous sequence of bytes used when performing I/O. The types [@boost:/doc/html/boost_asio/reference/const_buffer.html `net::const_buffer`] and [@boost:/doc/html/boost_asio/reference/mutable_buffer.html `net::mutable_buffer`] represent these memory regions as type-safe pointer/size pairs:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
`const_buffer` and `mutable_buffer` are preferred over `std::span<byte>`
`const_buffer` and `mutable_buffer` are preferred over `std::span<byte>`
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The concepts __ConstBufferSequence__ and __MutableBufferSequence__ describe bidirectional ranges whose value type is convertible to `const_buffer` and `mutable_buffer` respectively. These sequences allow transacting with multiple buffers in a single function call, a technique called [@https://en.wikipedia.org/wiki/Vectored_I/O ['scatter/gather I/O]]. Buffers and buffer sequences are non-owning; copies produce shallow references and not duplicates of the underlying memory. Each of these statements declares a buffer sequence:
The concepts __ConstBufferSequence__ and __MutableBufferSequence__ describe bidirectional ranges whose value type is convertible to `const_buffer` and `mutable_buffer` respectively. These sequences allow transacting with multiple buffers in a single function call, a technique called [@https://en.wikipedia.org/wiki/Vectored_I/O ['scatter/gather I/O]]. Buffers and buffer sequences are non-owning; copies produce shallow references and not duplicates of the underlying memory. Each of these statements declares a buffer sequence:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The functions [@boost:/doc/html/boost_asio/reference/buffer_size.html `net::buffer_size`] and [@boost:/doc/html/boost_asio/reference/buffer_copy.html `net::buffer_copy`] determine the total number of bytes in a buffer sequence, and transfer some or all of bytes from one buffer sequence to another respectively. The function `buffer_size` is a customization point: user defined overloads in foreign namespaces are possible, and callers should invoke `buffer_size` without namespace qualification. The functions [@boost:/doc/html/boost_asio/reference/buffer_sequence_begin.html `net::buffer_sequence_begin`] and [@boost:/doc/html/boost_asio/reference/buffer_sequence_end.html `net::buffer_sequence_end`] are used to obtain a pair of iterators for traversing the sequence. Beast provides a set of buffer sequence types and algorithms such as [link beast.ref.boost__beast__buffers_cat `buffers_cat`], [link beast.ref.boost__beast__buffers_front `buffers_front`], [link beast.ref.boost__beast__buffers_prefix `buffers_prefix`], [link beast.ref.boost__beast__buffers_range `buffers_range`], and [link beast.ref.boost__beast__buffers_suffix `buffers_suffix`]. This example returns the bytes in a buffer sequence as a string:
The functions [@boost:/doc/html/boost_asio/reference/buffer_size.html `net::buffer_size`] and [@boost:/doc/html/boost_asio/reference/buffer_copy.html `net::buffer_copy`] determine the total number of bytes in a buffer sequence, and transfer some or all of bytes from one buffer sequence to another respectively. The function `buffer_size` is a customization point: user defined overloads in foreign namespaces are possible, and callers should invoke `buffer_size` without namespace qualification. The functions [@boost:/doc/html/boost_asio/reference/buffer_sequence_begin.html `net::buffer_sequence_begin`] and [@boost:/doc/html/boost_asio/reference/buffer_sequence_end.html `net::buffer_sequence_end`] are used to obtain a pair of iterators for traversing the sequence. Beast provides a set of buffer sequence types and algorithms such as [link beast.ref.boost__beast__buffers_cat `buffers_cat`], [link beast.ref.boost__beast__buffers_front `buffers_front`], [link beast.ref.boost__beast__buffers_prefix `buffers_prefix`], [link beast.ref.boost__beast__buffers_range `buffers_range`], and [link beast.ref.boost__beast__buffers_suffix `buffers_suffix`]. This example returns the bytes in a buffer sequence as a string:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The __DynamicBuffer__ concept defines a resizable buffer sequence interface. Algorithms may be expressed in terms of dynamic buffers when the memory requirements are not known ahead of time, for example when reading an HTTP message from a stream. Beast provides a well-rounded collection of dynamic buffer types such as [link beast.ref.boost__beast__buffers_adaptor `buffers_adaptor`], [link beast.ref.boost__beast__flat_buffer `flat_buffer`], [link beast.ref.boost__beast__multi_buffer `multi_buffer`], and [link beast.ref.boost__beast__static_buffer `static_buffer`]. The following function reads data from a [link beast.ref.boost__beast__tcp_stream `tcp_stream`] into a dynamic buffer until it encountering a newline character, using [@boost:/doc/html/boost_asio/reference/buffers_iterator.html `net::buffers_iterator`] to treat the contents of the buffer as a range of characters:
The __DynamicBuffer__ concept defines a resizable buffer sequence interface. Algorithms may be expressed in terms of dynamic buffers when the memory requirements are not known ahead of time, for example when reading an HTTP message from a stream. Beast provides a well-rounded collection of dynamic buffer types such as [link beast.ref.boost__beast__buffers_adaptor `buffers_adaptor`], [link beast.ref.boost__beast__flat_buffer `flat_buffer`], [link beast.ref.boost__beast__multi_buffer `multi_buffer`], and [link beast.ref.boost__beast__static_buffer `static_buffer`]. The following function reads data from a [link beast.ref.boost__beast__tcp_stream `tcp_stream`] into a dynamic buffer until it encountering a newline character, using [@boost:/doc/html/boost_asio/reference/buffers_iterator.html `net::buffers_iterator`] to treat the contents of the buffer as a range of characters:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Synchronous I/O
Synchronous I/O
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Synchronous input and output is accomplished through blocking function calls that return with the result of the operation. Such operations typically cannot be canceled and do not have a method for setting a timeout. The __SyncReadStream__ and __SyncWriteStream__ concepts define requirements for ['synchronous streams]: a portable I/O abstraction that transfers data using buffer sequences to represent bytes and either `error_code` or an exception to report any failures. [@boost:/doc/html/boost_asio/reference/basic_stream_socket.html ['net::basic_stream_socket]] is a synchronous stream commonly used to form TCP/IP connections. User-defined types which meet the requirements are possible:
Synchronous input and output is accomplished through blocking function calls that return with the result of the operation. Such operations typically cannot be canceled and do not have a method for setting a timeout. The __SyncReadStream__ and __SyncWriteStream__ concepts define requirements for ['synchronous streams]: a portable I/O abstraction that transfers data using buffer sequences to represent bytes and either `error_code` or an exception to report any failures. [@boost:/doc/html/boost_asio/reference/basic_stream_socket.html ['net::basic_stream_socket]] is a synchronous stream commonly used to form TCP/IP connections. User-defined types which meet the requirements are possible:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
A ['synchronous stream algorithm] is written as a function template accepting a stream object meeting the named requirements for synchronous reading, writing, or both. This example shows an algorithm which writes text and uses exceptions to indicate errors:
A ['synchronous stream algorithm] is written as a function template accepting a stream object meeting the named requirements for synchronous reading, writing, or both. This example shows an algorithm which writes text and uses exceptions to indicate errors:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The same algorithm may be expressed using error codes instead of exceptions:
The same algorithm may be expressed using error codes instead of exceptions:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Asynchronous I/O
Asynchronous I/O
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
An asynchronous operation begins with a call to an [@boost:/doc/html/boost_asio/reference/asynchronous_operations.html ['initiating function]], which starts the operation and returns to the caller immediately. This ['outstanding] asynchronous operation proceeds concurrently without blocking the caller. When the externally observable side effects are fully established, a movable function object known as a [@boost:/doc/html/boost_asio/reference/CompletionHandler.html ['completion handler]] provided in the initiating function call is queued for execution with the results, which may include the error code and other specific information. An asynchronous operation is said to be ['completed] after the completion handler is queued. The code that follows shows how some text may be written to a socket asynchronously, invoking a lambda when the operation is complete:
An asynchronous operation begins with a call to an [@boost:/doc/html/boost_asio/reference/asynchronous_operations.html ['initiating function]], which starts the operation and returns to the caller immediately. This ['outstanding] asynchronous operation proceeds concurrently without blocking the caller. When the externally observable side effects are fully established, a movable function object known as a [@boost:/doc/html/boost_asio/reference/CompletionHandler.html ['completion handler]] provided in the initiating function call is queued for execution with the results, which may include the error code and other specific information. An asynchronous operation is said to be ['completed] after the completion handler is queued. The code that follows shows how some text may be written to a socket asynchronously, invoking a lambda when the operation is complete:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Every completion handler (also referred to as a [@https://en.wikipedia.org/wiki/Continuation ['continuation]]) has both an [@boost:/doc/html/boost_asio/overview/core/allocation.html ['associated allocator]] returned by [@boost:/doc/html/boost_asio/reference/get_associated_allocator.html `net::get_associated_allocator`], , an [@boost:/doc/html/boost_asio/reference/associated_cancellation_slot.html ['associated cancellation slot]] returned by [@boost:/doc/html/boost_asio/reference/associated_cancellation_slot.html `net::get_associated_cancellation_slot`]. and an [@boost:/doc/html/boost_asio/reference/associated_executor.html ['associated executor]] returned by [@boost:/doc/html/boost_asio/reference/get_associated_executor.html `net::get_associated_executor`]. These associations may be specified intrusively:
Every completion handler (also referred to as a [@https://en.wikipedia.org/wiki/Continuation ['continuation]]) has both an [@boost:/doc/html/boost_asio/overview/core/allocation.html ['associated allocator]] returned by [@boost:/doc/html/boost_asio/reference/get_associated_allocator.html `net::get_associated_allocator`], , an [@boost:/doc/html/boost_asio/reference/associated_cancellation_slot.html ['associated cancellation slot]] returned by [@boost:/doc/html/boost_asio/reference/associated_cancellation_slot.html `net::get_associated_cancellation_slot`]. and an [@boost:/doc/html/boost_asio/reference/associated_executor.html ['associated executor]] returned by [@boost:/doc/html/boost_asio/reference/get_associated_executor.html `net::get_associated_executor`]. These associations may be specified intrusively:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Or these associations may be specified non-intrusively, by specializing the class templates [@boost:/doc/html/boost_asio/reference/associated_allocator.html `net::associated_allocator`] , [@boost:/doc/html/boost_asio/reference/associated_cancellation_slot.html `net::associated_cancellation_slot`] and [@boost:/doc/html/boost_asio/reference/associated_executor.html `net::associated_executor`]:
Or these associations may be specified non-intrusively, by specializing the class templates [@boost:/doc/html/boost_asio/reference/associated_allocator.html `net::associated_allocator`] , [@boost:/doc/html/boost_asio/reference/associated_cancellation_slot.html `net::associated_cancellation_slot`] and [@boost:/doc/html/boost_asio/reference/associated_executor.html `net::associated_executor`]:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The function [@boost:/doc/html/boost_asio/reference/bind_executor.html `net::bind_executor`] may be used when the caller wants to change the executor of a completion handler.
The function [@boost:/doc/html/boost_asio/reference/bind_executor.html `net::bind_executor`] may be used when the caller wants to change the executor of a completion handler.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The allocator is used by the implementation to obtain any temporary storage necessary to perform the operation. Temporary allocations are always freed before the completion handler is invoked. The executor is a cheaply copyable object providing the algorithm used to invoke the completion handler. Unless customized by the caller, a completion handler defaults to using `std::allocator<void>` and the executor of the corresponding I/O object.
The allocator is used by the implementation to obtain any temporary storage necessary to perform the operation. Temporary allocations are always freed before the completion handler is invoked. The executor is a cheaply copyable object providing the algorithm used to invoke the completion handler. Unless customized by the caller, a completion handler defaults to using `std::allocator<void>` and the executor of the corresponding I/O object.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The function [@boost:/doc/html/boost_asio/reference/bind_allocator.html `net::bind_allocator`] can be used when the caller wants to assign a custom allocator to the operation.
The function [@boost:/doc/html/boost_asio/reference/bind_allocator.html `net::bind_allocator`] can be used when the caller wants to assign a custom allocator to the operation.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
A completion token's associated cancellation_slot can be used to cancel single operations. This is often passed through by the completion token such as [@boost:/doc/html/boost_asio/reference/use_awaitable.html `net::use_awaitable`] or [@boost:/doc/html/boost_asio/reference/yield_context.html `net::yield_context`] .
A completion token's associated cancellation_slot can be used to cancel single operations. This is often passed through by the completion token such as [@boost:/doc/html/boost_asio/reference/use_awaitable.html `net::use_awaitable`] or [@boost:/doc/html/boost_asio/reference/yield_context.html `net::yield_context`] .
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The available [@boost:/doc/html/boost_asio/reference/cancellation_type.html cancellation types] are listed below.
The available [@boost:/doc/html/boost_asio/reference/cancellation_type.html cancellation types] are listed below.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Networking prescribes facilities to determine the context in which handlers run. Every I/O object refers to an __ExecutionContext__ for obtaining the __Executor__ instance used to invoke completion handlers. An executor determines where and how completion handlers are invoked. Executors obtained from an instance of __io_context__ offer a basic guarantee: handlers will only be invoked from threads which are currently calling [@boost:/doc/html/boost_asio/reference/io_context/run/overload1.html `net::io_context::run`].
Networking prescribes facilities to determine the context in which handlers run. Every I/O object refers to an __ExecutionContext__ for obtaining the __Executor__ instance used to invoke completion handlers. An executor determines where and how completion handlers are invoked. Executors obtained from an instance of __io_context__ offer a basic guarantee: handlers will only be invoked from threads which are currently calling [@boost:/doc/html/boost_asio/reference/io_context/run/overload1.html `net::io_context::run`].
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The __AsyncReadStream__ and __AsyncWriteStream__ concepts define requirements for ['asynchronous streams]: a portable I/O abstraction that exchanges data asynchronously using buffer sequences to represent bytes and `error_code` to report any failures. An ['asynchronous stream algorithm] is written as a templated initiating function template accepting a stream object meeting the named requirements for asynchronous reading, writing, or both. This example shows an algorithm which writes some text to an asynchronous stream:
The __AsyncReadStream__ and __AsyncWriteStream__ concepts define requirements for ['asynchronous streams]: a portable I/O abstraction that exchanges data asynchronously using buffer sequences to represent bytes and `error_code` to report any failures. An ['asynchronous stream algorithm] is written as a templated initiating function template accepting a stream object meeting the named requirements for asynchronous reading, writing, or both. This example shows an algorithm which writes some text to an asynchronous stream:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Concurrency
Concurrency
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
I/O objects such as sockets and streams [*are not thread-safe]. Although it is possible to have more than one operation outstanding (for example, a simultaneous asynchronous read and asynchronous write) the stream object itself may only be accessed from one thread at a time. This means that member functions such as move constructors, destructors, or initiating functions must not be called concurrently. Usually this is accomplished with synchronization primitives such as a [@https://en.cppreference.com/w/cpp/thread/mutex `mutex`], but concurrent network programs need a better way to access shared resources, since acquiring ownership of a mutex could block threads from performing uncontended work. For efficiency, networking adopts a model of using threads without explicit locking by requiring all access to I/O objects to be performed within a [@boost:/doc/html/boost_asio/overview/core/strands.html ['strand]].
I/O objects such as sockets and streams [*are not thread-safe]. Although it is possible to have more than one operation outstanding (for example, a simultaneous asynchronous read and asynchronous write) the stream object itself may only be accessed from one thread at a time. This means that member functions such as move constructors, destructors, or initiating functions must not be called concurrently. Usually this is accomplished with synchronization primitives such as a [@https://en.cppreference.com/w/cpp/thread/mutex `mutex`], but concurrent network programs need a better way to access shared resources, since acquiring ownership of a mutex could block threads from performing uncontended work. For efficiency, networking adopts a model of using threads without explicit locking by requiring all access to I/O objects to be performed within a [@boost:/doc/html/boost_asio/overview/core/strands.html ['strand]].
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Because completion handlers cause an inversion of the flow of control, sometimes other methods of attaching a continuation are desired. Networking provides the [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3747.pdf ['Universal Model for Asynchronous Operations]], providing a customizable means for transforming the signature of the initiating function to use other types of objects and methods in place of a completion handler callback. For example to call to write a string to a socket asynchronously, using a `std::future` to receive the number of bytes transferred thus looks like this:
Because completion handlers cause an inversion of the flow of control, sometimes other methods of attaching a continuation are desired. Networking provides the [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3747.pdf ['Universal Model for Asynchronous Operations]], providing a customizable means for transforming the signature of the initiating function to use other types of objects and methods in place of a completion handler callback. For example to call to write a string to a socket asynchronously, using a `std::future` to receive the number of bytes transferred thus looks like this:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
This functionality is enabled by passing the variable [@boost:/doc/html/boost_asio/reference/use_future.html `net::use_future`] (of type [@boost:/doc/html/boost_asio/reference/use_future_t.html `net::use_future_t<>`]) in place of the completion handler. The same `async_write` function overload can work with a [@https://en.wikipedia.org/wiki/Fiber_(computer_science) ['fiber]] launched with [@boost:/doc/html/boost_asio/reference/spawn/overload1.html `asio::spawn`]:
This functionality is enabled by passing the variable [@boost:/doc/html/boost_asio/reference/use_future.html `net::use_future`] (of type [@boost:/doc/html/boost_asio/reference/use_future_t.html `net::use_future_t<>`]) in place of the completion handler. The same `async_write` function overload can work with a [@https://en.wikipedia.org/wiki/Fiber_(computer_science) ['fiber]] launched with [@boost:/doc/html/boost_asio/reference/spawn/overload1.html `asio::spawn`]:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
In both of these cases, an object with a specific type is used in place of the completion handler, and the return value of the initiating function is transformed from `void` to `std::future<std::size_t>` or `std::size_t`. The handler is sometimes called a __CompletionToken__ when used in this context. The return type transformation is supported by customization points in the initiating function signature. Here is the signature for [@boost:/doc/html/boost_asio/reference/async_write/overload1.html `net::async_write`]:
In both of these cases, an object with a specific type is used in place of the completion handler, and the return value of the initiating function is transformed from `void` to `std::future<std::size_t>` or `std::size_t`. The handler is sometimes called a __CompletionToken__ when used in this context. The return type transformation is supported by customization points in the initiating function signature. Here is the signature for [@boost:/doc/html/boost_asio/reference/async_write/overload1.html `net::async_write`]:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Note that a `spawn` function itself has a completion signature, but we're ignoring it's result in the example by using `asio::detached`.
Note that a `spawn` function itself has a completion signature, but we're ignoring it's result in the example by using `asio::detached`.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
The type of the function's return value is determined by the [@boost:/doc/html/boost_asio/reference/async_result.html `net::async_result`] customization point, which comes with specializations for common library types such as `std::future` and may also be specialized for user-defined types. The body of the initiating function calls the [@boost:/doc/html/boost_asio/reference/async_initiate.html `net::async_initiate`] helper to capture the arguments and forward them to the specialization of `async_result`. An additional "initiation function" object is provided which `async_result` may use to immediately launch the operation, or defer the launch of the operation until some point in the future (this is called "lazy execution"). The initiation function object receives the internal completion handler which matches the signature expected by the initiating function:
The type of the function's return value is determined by the [@boost:/doc/html/boost_asio/reference/async_result.html `net::async_result`] customization point, which comes with specializations for common library types such as `std::future` and may also be specialized for user-defined types. The body of the initiating function calls the [@boost:/doc/html/boost_asio/reference/async_initiate.html `net::async_initiate`] helper to capture the arguments and forward them to the specialization of `async_result`. An additional "initiation function" object is provided which `async_result` may use to immediately launch the operation, or defer the launch of the operation until some point in the future (this is called "lazy execution"). The initiation function object receives the internal completion handler which matches the signature expected by the initiating function:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
This transformed, internal handler is responsible for the finalizing step that delivers the result of the operation to the caller. For example, when using `net::use_future` the internal handler will deliver the result by calling [@https://en.cppreference.com/w/cpp/thread/promise/set_value `std::promise::set_value`] on the promise object returned by the initiating function.
This transformed, internal handler is responsible for the finalizing step that delivers the result of the operation to the caller. For example, when using `net::use_future` the internal handler will deliver the result by calling [@https://en.cppreference.com/w/cpp/thread/promise/set_value `std::promise::set_value`] on the promise object returned by the initiating function.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Using Networking
Using Networking
Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)
Most library stream algorithms require a __socket__, __ssl_stream__, or other __Stream__ object that has already established communication with a remote peer. This example is provided as a reminder of how to work with sockets:
Most library stream algorithms require a __socket__, __ssl_stream__, or other __Stream__ object that has already established communication with a remote peer. This example is provided as a reminder of how to work with sockets: