2. Boost Beast Translation (zh_Hans)
3. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

has:check

Component and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location
• Component and priority

	Translation	Source string	Target string
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	Throughout this documentation identifiers with the following names have special meaning:	Throughout this documentation identifiers with the following names have special meaning:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	[@boost:/doc/html/boost_asio/reference/io_context.html [*`ioc`]]	[@boost:/doc/html/boost_asio/reference/io_context.html [*`ioc`]]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	A variable of type __io_context__ which is running on one separate thread, and upon which an __executor_work_guard__ object has been constructed.	A variable of type __io_context__ which is running on one separate thread, and upon which an __executor_work_guard__ object has been constructed.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	[@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html [*`sock`]]	[@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html [*`sock`]]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	A variable of type [@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html `tcp::socket`] which has already been connected to a remote host.	A variable of type [@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html `tcp::socket`] which has already been connected to a remote host.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	[@boost:/doc/html/boost_asio/reference/ssl__stream.html [*`ssl_sock`]]	[@boost:/doc/html/boost_asio/reference/ssl__stream.html [*`ssl_sock`]]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	A variable of type [@boost:/doc/html/boost_asio/reference/ssl__stream.html `net::ssl::stream<tcp::socket>`] which is already connected and has handshaked with a remote host.	A variable of type [@boost:/doc/html/boost_asio/reference/ssl__stream.html `net::ssl::stream<tcp::socket>`] which is already connected and has handshaked with a remote host.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__websocket__stream [*`ws`]]	[link beast.ref.boost__beast__websocket__stream [*`ws`]]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 1 Refresher (qbk) — Chinese (Simplified Han script)	A variable of type [link beast.ref.boost__beast__websocket__stream `websocket::stream<tcp::socket>`] which is already connected with a remote host.	A variable of type [link beast.ref.boost__beast__websocket__stream `websocket::stream<tcp::socket>`] which is already connected with a remote host.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	A secure SSL/TLS connection requires a proper shutdown process to securely indicate the [@https://en.wikipedia.org/wiki/End-of-file ['EOF]] condition. This process prevents a type of attack known as a [@https://en.wikipedia.org/wiki/Transport_Layer_Security#Truncation_attack ['truncation attack]] in which an attacker can close the underlying transport layer and control the length of the last message in the SSL/TLS connection. A shutdown process consists of exchanging `close_notify` message between two parties. In __Asio__ these steps happen by calling `shutdown()` or `async_shutdown()` on `ssl::stream` object.	A secure SSL/TLS connection requires a proper shutdown process to securely indicate the [@https://en.wikipedia.org/wiki/End-of-file ['EOF]] condition. This process prevents a type of attack known as a [@https://en.wikipedia.org/wiki/Transport_Layer_Security#Truncation_attack ['truncation attack]] in which an attacker can close the underlying transport layer and control the length of the last message in the SSL/TLS connection. A shutdown process consists of exchanging `close_notify` message between two parties. In __Asio__ these steps happen by calling `shutdown()` or `async_shutdown()` on `ssl::stream` object.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	error::stream_truncated	error::stream_truncated
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	There are SSL/TLS implementations that don't perform a proper shutdown process and simply close the underlying transport layer instead. As a result, the EOF condition in these applications is not cryptographically secure and should not be relied upon. However, there are scenarios where an HTTPS client or server doesn't need EOF for determining the end of the last message:	There are SSL/TLS implementations that don't perform a proper shutdown process and simply close the underlying transport layer instead. As a result, the EOF condition in these applications is not cryptographically secure and should not be relied upon. However, there are scenarios where an HTTPS client or server doesn't need EOF for determining the end of the last message:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	* The HTTP message has a `Content-Length` header, and the body is fully	* The HTTP message has a `Content-Length` header, and the body is fully
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	* The HTTP message uses chunked transfer encoding, and the final chunk is	* The HTTP message uses chunked transfer encoding, and the final chunk is
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	* The HTTP message doesn't contain a body, such as any response with a 1xx	* The HTTP message doesn't contain a body, such as any response with a 1xx
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	In such scenarios, `http::read` or `http::async_read` operations succeed as they don't need EOF to complete. However, the next operation on the stream would fail with an [@boost:/doc/html/boost_asio/reference/ssl__error__stream_errors.html `net::ssl::error::stream_truncated`] error.	In such scenarios, `http::read` or `http::async_read` operations succeed as they don't need EOF to complete. However, the next operation on the stream would fail with an [@boost:/doc/html/boost_asio/reference/ssl__error__stream_errors.html `net::ssl::error::stream_truncated`] error.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	For example, let's assume we are using Beast for communicating with an HTTPS server that doesn't perform a proper SSL/TLS shutdown:	For example, let's assume we are using Beast for communicating with an HTTPS server that doesn't perform a proper SSL/TLS shutdown:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	Non-Compliant Peers and Unknown Body Length	Non-Compliant Peers and Unknown Body Length
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	This is a rare case and indeed a security issue when HTTPS servers don't perform a proper SSL/TLS shutdown procedure and send an HTTP response message that relies on EOF to determine the end of the body. This is a security concern because without an SSL/TLS shutdown procedure, the EOF is not cryptographically secure, leaving the message body vulnerable to truncation attacks.	This is a rare case and indeed a security issue when HTTPS servers don't perform a proper SSL/TLS shutdown procedure and send an HTTP response message that relies on EOF to determine the end of the body. This is a security concern because without an SSL/TLS shutdown procedure, the EOF is not cryptographically secure, leaving the message body vulnerable to truncation attacks.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 10 Ssl Tls Shutdown (qbk) — Chinese (Simplified Han script)	The following is an example that can read an HTTP response from such a server:	The following is an example that can read an HTTP response from such a server:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	A __Stream__ is a communication channel where data is reliably transferred as an ordered sequence of bytes. Streams are either synchronous or asynchronous, and may allow reading, writing, or both. Note that a particular type may model more than one concept. For example, the networking types __socket__ and __ssl_stream__ support both __SyncStream__ and __AsyncStream__. All stream algorithms in Beast are declared as template functions using these concepts:	A __Stream__ is a communication channel where data is reliably transferred as an ordered sequence of bytes. Streams are either synchronous or asynchronous, and may allow reading, writing, or both. Note that a particular type may model more than one concept. For example, the networking types __socket__ and __ssl_stream__ support both __SyncStream__ and __AsyncStream__. All stream algorithms in Beast are declared as template functions using these concepts:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Stream Concepts	Stream Concepts
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Concept	Concept
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	__SyncReadStream__	__SyncReadStream__
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Supports buffer-oriented blocking reads.	Supports buffer-oriented blocking reads.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	__SyncWriteStream__	__SyncWriteStream__
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Supports buffer-oriented blocking writes.	Supports buffer-oriented blocking writes.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	__SyncStream__	__SyncStream__
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	A stream supporting buffer-oriented blocking reads and writes.	A stream supporting buffer-oriented blocking reads and writes.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	__AsyncReadStream__	__AsyncReadStream__
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Supports buffer-oriented asynchronous reads.	Supports buffer-oriented asynchronous reads.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	__AsyncWriteStream__	__AsyncWriteStream__
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Supports buffer-oriented asynchronous writes.	Supports buffer-oriented asynchronous writes.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	__AsyncStream__	__AsyncStream__
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	A stream supporting buffer-oriented asynchronous reads and writes.	A stream supporting buffer-oriented asynchronous reads and writes.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	These template metafunctions check whether a given type meets the requirements for the various stream concepts, and some additional useful utilities. The library uses these type checks internally and also provides them as public interfaces so users may use the same techniques to augment their own code. The use of these type checks helps provide more concise errors during compilation:	These template metafunctions check whether a given type meets the requirements for the various stream concepts, and some additional useful utilities. The library uses these type checks internally and also provides them as public interfaces so users may use the same techniques to augment their own code. The use of these type checks helps provide more concise errors during compilation:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Type Traits and Metafunctions	Type Traits and Metafunctions
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__executor_type `executor_type`]	[link beast.ref.boost__beast__executor_type `executor_type`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	An alias for the type of object returned by `get_executor`.	An alias for the type of object returned by `get_executor`.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__has_get_executor `has_get_executor`]	[link beast.ref.boost__beast__has_get_executor `has_get_executor`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Determine if the `get_executor` member function is present.	Determine if the `get_executor` member function is present.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__is_async_read_stream `is_async_read_stream`]	[link beast.ref.boost__beast__is_async_read_stream `is_async_read_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Determine if a type meets the requirements of __AsyncReadStream__.	Determine if a type meets the requirements of __AsyncReadStream__.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__is_async_stream `is_async_stream`]	[link beast.ref.boost__beast__is_async_stream `is_async_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Determine if a type meets the requirements of both __AsyncReadStream__ and __AsyncWriteStream__.	Determine if a type meets the requirements of both __AsyncReadStream__ and __AsyncWriteStream__.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__is_async_write_stream `is_async_write_stream`]	[link beast.ref.boost__beast__is_async_write_stream `is_async_write_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Determine if a type meets the requirements of __AsyncWriteStream__.	Determine if a type meets the requirements of __AsyncWriteStream__.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__is_sync_read_stream `is_sync_read_stream`]	[link beast.ref.boost__beast__is_sync_read_stream `is_sync_read_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Determine if a type meets the requirements of __SyncReadStream__.	Determine if a type meets the requirements of __SyncReadStream__.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__is_sync_stream `is_sync_stream`]	[link beast.ref.boost__beast__is_sync_stream `is_sync_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Determine if a type meets the requirements of both __SyncReadStream__ and __SyncWriteStream__.	Determine if a type meets the requirements of both __SyncReadStream__ and __SyncWriteStream__.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__is_sync_write_stream `is_sync_write_stream`]	[link beast.ref.boost__beast__is_sync_write_stream `is_sync_write_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Determine if a type meets the requirements of __SyncWriteStream__.	Determine if a type meets the requirements of __SyncWriteStream__.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 2 Streams (qbk) — Chinese (Simplified Han script)	Using the type checks with `static_assert` on function or class template types will provide users with helpful error messages and prevent undefined behaviors. This example shows how a template function which writes to a synchronous stream may check its argument:	Using the type checks with `static_assert` on function or class template types will provide users with helpful error messages and prevent undefined behaviors. This example shows how a template function which writes to a synchronous stream may check its argument:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Timeouts __example__	Timeouts __example__
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Network programs must handle adverse connection conditions; the most common is that a connected peer goes offline unexpectedly. Protocols have no way of identifying this reliably: the peer is offline after all, and unable to send a message announcing the absence. A peer can go offline for various reasons:	Network programs must handle adverse connection conditions; the most common is that a connected peer goes offline unexpectedly. Protocols have no way of identifying this reliably: the peer is offline after all, and unable to send a message announcing the absence. A peer can go offline for various reasons:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	To determine when a peer is offline or idle, a program will implement a [@https://en.wikipedia.org/wiki/Timeout_(computing) timeout] algorithm, which closes the connection after a specified amount of time if some condition is met. For example, if no data is received for the duration. A timeout may be used to:	To determine when a peer is offline or idle, a program will implement a [@https://en.wikipedia.org/wiki/Timeout_(computing) timeout] algorithm, which closes the connection after a specified amount of time if some condition is met. For example, if no data is received for the duration. A timeout may be used to:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Traditionally, programs use a [@boost:/doc/html/boost_asio/reference/steady_timer.html `net::steady_timer`] to determine when a timeout occurs, and then call [@boost:/doc/html/boost_asio/reference/basic_socket/close/overload2.html `close`] on the socket to release the resources. The complexity of managing a separate timer is often a source of [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1269r0.html#timers frustration] for non-experts.	Traditionally, programs use a [@boost:/doc/html/boost_asio/reference/steady_timer.html `net::steady_timer`] to determine when a timeout occurs, and then call [@boost:/doc/html/boost_asio/reference/basic_socket/close/overload2.html `close`] on the socket to release the resources. The complexity of managing a separate timer is often a source of [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1269r0.html#timers frustration] for non-experts.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	For portability reasons, networking does not provide timeouts	For portability reasons, networking does not provide timeouts
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	To simplify the handling of timeouts, these provided types wrap a [@boost:/doc/html/boost_asio/reference/basic_stream_socket.html `net::basic_stream_socket`] to provide additional features:	To simplify the handling of timeouts, these provided types wrap a [@boost:/doc/html/boost_asio/reference/basic_stream_socket.html `net::basic_stream_socket`] to provide additional features:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__tcp_stream `tcp_stream`]	[link beast.ref.boost__beast__tcp_stream `tcp_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	[itemized_list [Timeouts for logical operations] [[@boost:/doc/html/boost_asio/reference/ip__tcp.html `net::ip::tcp`] protocol] [[@boost:/doc/html/boost_asio/reference/executor.html `net::executor`] executor] [[link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`] rate limits] ]	[itemized_list [Timeouts for logical operations] [[@boost:/doc/html/boost_asio/reference/ip__tcp.html `net::ip::tcp`] protocol] [[@boost:/doc/html/boost_asio/reference/executor.html `net::executor`] executor] [[link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`] rate limits] ]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__basic_stream `basic_stream`]	[link beast.ref.boost__beast__basic_stream `basic_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	[itemized_list [Timeouts for logical operations] [Configurable __Protocol__ type] [Configurable __Executor__ type] [Configurable __RatePolicy__ type] ]	[itemized_list [Timeouts for logical operations] [Configurable __Protocol__ type] [Configurable __Executor__ type] [Configurable __RatePolicy__ type] ]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Construction	Construction
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	The `tcp_stream` is designed as a replacement for [@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html `net::ip::tcp::socket`]. Any program which currently uses a socket, can switch to a `tcp_stream` and achieve the features above (although some interfaces are different, see below). Networking now allows I/O objects to construct with any instance of __ExecutionContext__ or __Executor__ objects. Here we construct a stream which uses a particular I/O context to dispatch completion handlers:	The `tcp_stream` is designed as a replacement for [@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html `net::ip::tcp::socket`]. Any program which currently uses a socket, can switch to a `tcp_stream` and achieve the features above (although some interfaces are different, see below). Networking now allows I/O objects to construct with any instance of __ExecutionContext__ or __Executor__ objects. Here we construct a stream which uses a particular I/O context to dispatch completion handlers:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Alternatively, we can construct the stream from an executor:	Alternatively, we can construct the stream from an executor:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	The function [@boost:/doc/html/boost_asio/reference/make_strand.html `make_strand`] returns a strand constructed from an execution context or executor. When a [@boost:/doc/html/boost_asio/reference/strand.html `net::strand`] is chosen for the stream's executor, all completion handlers which do not already have an associated executor will use the strand. This is both a notational convenience (no need for `strand::wrap` or `bind_executor` at call sites) and a measure of safety, as it is no longer possible to forget to use the strand.	The function [@boost:/doc/html/boost_asio/reference/make_strand.html `make_strand`] returns a strand constructed from an execution context or executor. When a [@boost:/doc/html/boost_asio/reference/strand.html `net::strand`] is chosen for the stream's executor, all completion handlers which do not already have an associated executor will use the strand. This is both a notational convenience (no need for `strand::wrap` or `bind_executor` at call sites) and a measure of safety, as it is no longer possible to forget to use the strand.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Connecting	Connecting
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Before data can be exchanged, the stream needs to be connected to a peer. The following code sets a timeout for an asynchronous connect operation. In Beast, functions to connect to a range of endpoints (such as the range returned by [@boost:/doc/html/boost_asio/reference/ip__basic_resolver/resolve/overload3.html `net::ip::tcp::resolver::resolve`]) are members of the class rather than free functions such as [@boost:/doc/html/boost_asio/reference/async_connect.html `net::async_connect`].	Before data can be exchanged, the stream needs to be connected to a peer. The following code sets a timeout for an asynchronous connect operation. In Beast, functions to connect to a range of endpoints (such as the range returned by [@boost:/doc/html/boost_asio/reference/ip__basic_resolver/resolve/overload3.html `net::ip::tcp::resolver::resolve`]) are members of the class rather than free functions such as [@boost:/doc/html/boost_asio/reference/async_connect.html `net::async_connect`].
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	A server will use an acceptor bound to a particular IP address and port to listen to and receive incoming connection requests. The acceptor returns an ordinary socket. A `tcp_stream` can be move-constructed from the underlying `basic_stream_socket` thusly:	A server will use an acceptor bound to a particular IP address and port to listen to and receive incoming connection requests. The acceptor returns an ordinary socket. A `tcp_stream` can be move-constructed from the underlying `basic_stream_socket` thusly:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Reading and Writing	Reading and Writing
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Timeouts apply to the logical operation, expressed as a series of asynchronous calls, rather than just the next call. This code reads a line from the stream and writes it back. Both the read and the write must complete within 30 seconds from when the timeout was set; the timer is not reset between operations.	Timeouts apply to the logical operation, expressed as a series of asynchronous calls, rather than just the next call. This code reads a line from the stream and writes it back. Both the read and the write must complete within 30 seconds from when the timeout was set; the timer is not reset between operations.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Since reads and writes can take place concurrently, it is possible to have two simultaneous logical operations where each operation either only reads, or only writes. The beginning of a new read or write operation will use the most recently set timeout. This will not affect operations that are already outstanding.	Since reads and writes can take place concurrently, it is possible to have two simultaneous logical operations where each operation either only reads, or only writes. The beginning of a new read or write operation will use the most recently set timeout. This will not affect operations that are already outstanding.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	When a timeout is set, it cancels any previous read or write timeout for which no outstanding operation is in progress. Algorithms which loop over logical operations simply need to set the timeout once before the logical operation, it is not necessary to call `expires_never` in this case. Here we implement an algorithm which continuously echoes lines back, with a timeout. This example is implemented as a complete function.	When a timeout is set, it cancels any previous read or write timeout for which no outstanding operation is in progress. Algorithms which loop over logical operations simply need to set the timeout once before the logical operation, it is not necessary to call `expires_never` in this case. Here we implement an algorithm which continuously echoes lines back, with a timeout. This example is implemented as a complete function.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	It is important to note that all of the examples thus far which perform reads and writes with a timeout, make use of the existing networking stream algorithms. As these algorithms are written generically to work with any object meeting the stream requirements, they transparently support timeouts when used with `tcp_stream`. This can be used to enable timeouts for stream wrappers that do not currently support timeouts.	It is important to note that all of the examples thus far which perform reads and writes with a timeout, make use of the existing networking stream algorithms. As these algorithms are written generically to work with any object meeting the stream requirements, they transparently support timeouts when used with `tcp_stream`. This can be used to enable timeouts for stream wrappers that do not currently support timeouts.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	The following code establishes an encrypted connection, writes an HTTP request, reads the HTTP response, and closes the connection gracefully. If these operations take longer than 30 seconds total, a timeout occurs. This code is intended to show how `tcp_stream` can be used to enable timeouts across unmodified stream algorithms which were not originally written to support timing out, and how a blocking algorithm may be written from asynchronous intermediate operations.	The following code establishes an encrypted connection, writes an HTTP request, reads the HTTP response, and closes the connection gracefully. If these operations take longer than 30 seconds total, a timeout occurs. This code is intended to show how `tcp_stream` can be used to enable timeouts across unmodified stream algorithms which were not originally written to support timing out, and how a blocking algorithm may be written from asynchronous intermediate operations.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Rate Limiting __example__	Rate Limiting __example__
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	The [link beast.ref.boost__beast__basic_stream `basic_stream`] class template supports an additional `RatePolicy` template parameter. Objects of this type must meet the requirements of __RatePolicy__. They are used to implement rate limiting or bandwidth management. The default policy for `basic_stream` and `tcp_stream` is [link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`], which places no limits on reading and writing. The library comes with the [link beast.ref.boost__beast__simple_rate_policy `simple_rate_policy`], allowing for independent control of read and write limits expressed in terms of bytes per second. The follow code creates an instance of the basic stream with a simple rate policy, and sets the read and write limits:	The [link beast.ref.boost__beast__basic_stream `basic_stream`] class template supports an additional `RatePolicy` template parameter. Objects of this type must meet the requirements of __RatePolicy__. They are used to implement rate limiting or bandwidth management. The default policy for `basic_stream` and `tcp_stream` is [link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`], which places no limits on reading and writing. The library comes with the [link beast.ref.boost__beast__simple_rate_policy `simple_rate_policy`], allowing for independent control of read and write limits expressed in terms of bytes per second. The follow code creates an instance of the basic stream with a simple rate policy, and sets the read and write limits:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	More sophisticated rate policies can be implemented as user-defined types which meet the requirements of __RatePolicy__. Here, we develop a rate policy that measures the instantaneous throughput of reads and writes. First we write a small utility class that applies an exponential smoothing function to a series of discrete rate samples, to calculate instantaneous throughput.	More sophisticated rate policies can be implemented as user-defined types which meet the requirements of __RatePolicy__. Here, we develop a rate policy that measures the instantaneous throughput of reads and writes. First we write a small utility class that applies an exponential smoothing function to a series of discrete rate samples, to calculate instantaneous throughput.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	Then we define our rate policy object. We friend the type [link beast.ref.boost__beast__rate_policy_access `rate_policy_access`] to allow our implementation to be private, but still allow the `basic_stream` access to call the required functions. This lets us avoid having to write a cumbersome friend declaration for the `basic_stream` class template. Public members of rate policy objects become part of the stream object's interface, through a call to `rate_policy`.	Then we define our rate policy object. We friend the type [link beast.ref.boost__beast__rate_policy_access `rate_policy_access`] to allow our implementation to be private, but still allow the `basic_stream` access to call the required functions. This lets us avoid having to write a cumbersome friend declaration for the `basic_stream` class template. Public members of rate policy objects become part of the stream object's interface, through a call to `rate_policy`.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 3 Timeouts (qbk) — Chinese (Simplified Han script)	To use our new policy we declare an instance of the stream, and then use it with stream algorithms as usual. At any time, we can determine the current read or write rates by calling into the policy.	To use our new policy we declare an instance of the stream, and then use it with stream algorithms as usual. At any time, we can determine the current read or write rates by calling into the policy.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	Layered Streams	Layered Streams
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	Networking's __ssl_stream__ is a class template meeting the requirements of both synchronous and asynchronous read and write streams, implemented in terms of a "next layer" object whose type is determined by a class template parameter. The SSL stream constructs an instance of the next layer object internally, while allowing external access through the observer `net::ssl::stream::next_layer()`. This declares an SSL stream which uses a regular TCP/IP socket as the next layer:	Networking's __ssl_stream__ is a class template meeting the requirements of both synchronous and asynchronous read and write streams, implemented in terms of a "next layer" object whose type is determined by a class template parameter. The SSL stream constructs an instance of the next layer object internally, while allowing external access through the observer `net::ssl::stream::next_layer()`. This declares an SSL stream which uses a regular TCP/IP socket as the next layer:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	Objects using this design pattern are referred to in networking as "a stack of stream layers". In Beast we use the term ['layered stream], although the property of having a next layer is not exclusive to streams. As with the SSL stream, __websocket_stream__ is a class template parameterized on a next layer object. This declares a websocket stream which uses a regular TCP/IP socket as the next layer:	Objects using this design pattern are referred to in networking as "a stack of stream layers". In Beast we use the term ['layered stream], although the property of having a next layer is not exclusive to streams. As with the SSL stream, __websocket_stream__ is a class template parameterized on a next layer object. This declares a websocket stream which uses a regular TCP/IP socket as the next layer:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	If a Secure WebSockets stream is desired, this is accomplished simply by changing the type of the next layer and adjusting the constructor arguments to match:	If a Secure WebSockets stream is desired, this is accomplished simply by changing the type of the next layer and adjusting the constructor arguments to match:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	Higher level abstractions can be developed in this fashion by nesting stream layers to arbitrary degree. The stack of stream layers effectively forms a compile-time singly linked list. The object at the end of this list is called the ['lowest layer], and is special from the others because it typically represents the underlying socket.	Higher level abstractions can be developed in this fashion by nesting stream layers to arbitrary degree. The stack of stream layers effectively forms a compile-time singly linked list. The object at the end of this list is called the ['lowest layer], and is special from the others because it typically represents the underlying socket.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	Beast comes with several layered stream wrappers, as well as facilities for authoring and working with layered streams:	Beast comes with several layered stream wrappers, as well as facilities for authoring and working with layered streams:
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	Layered Stream Algorithms and Types	Layered Stream Algorithms and Types
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__basic_stream `basic_stream`] [link beast.ref.boost__beast__tcp_stream `tcp_stream`]	[link beast.ref.boost__beast__basic_stream `basic_stream`] [link beast.ref.boost__beast__tcp_stream `tcp_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	This stream can be used for synchronous and asynchronous reading and writing. It allows timeouts to be set on logical operations, and can have an executor associated with the stream which is used to invoke completion handlers. This lets you set a strand on the stream once, which is then used for all asynchronous operations automatically.	This stream can be used for synchronous and asynchronous reading and writing. It allows timeouts to be set on logical operations, and can have an executor associated with the stream which is used to invoke completion handlers. This lets you set a strand on the stream once, which is then used for all asynchronous operations automatically.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__buffered_read_stream `buffered_read_stream`]	[link beast.ref.boost__beast__buffered_read_stream `buffered_read_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	A buffered read stream meets the requirements for synchronous and asynchronous read and write streams, and additionally implements configurable buffering for reads.	A buffered read stream meets the requirements for synchronous and asynchronous read and write streams, and additionally implements configurable buffering for reads.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__close_socket `close_socket`]	[link beast.ref.boost__beast__close_socket `close_socket`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	This function closes a socket by performing an unqualified call to the [link beast.ref.boost__beast__beast_close_socket `beast_close_socket`] customization point, allowing sockets to be closed in generic contexts in an extensible fashion.	This function closes a socket by performing an unqualified call to the [link beast.ref.boost__beast__beast_close_socket `beast_close_socket`] customization point, allowing sockets to be closed in generic contexts in an extensible fashion.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__get_lowest_layer `get_lowest_layer`]	[link beast.ref.boost__beast__get_lowest_layer `get_lowest_layer`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	Returns the lowest layer in a stack of stream layers by recursively calling the `next_layer` member function on each object until reaching an object which lacks the member. This example puts a layered stream into non-blocking mode by retrieving the TCP/IP socket in the lowest layer and changing the socket option: [code_core_4_layers_4]	Returns the lowest layer in a stack of stream layers by recursively calling the `next_layer` member function on each object until reaching an object which lacks the member. This example puts a layered stream into non-blocking mode by retrieving the TCP/IP socket in the lowest layer and changing the socket option: [code_core_4_layers_4]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__http__icy_stream `http::icy_stream`]	[link beast.ref.boost__beast__http__icy_stream `http::icy_stream`]
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	An ICY stream transparently converts the non-standard "ICY 200 OK" HTTP response from Shoutcast servers into a conforming 200 level HTTP response.	An ICY stream transparently converts the non-standard "ICY 200 OK" HTTP response from Shoutcast servers into a conforming 200 level HTTP response.
	Boost Beast Translation (zh_Hans)/Doc / Qbk / 03 Core / 4 Layers (qbk) — Chinese (Simplified Han script)	[link beast.ref.boost__beast__lowest_layer_type `lowest_layer_type`]	[link beast.ref.boost__beast__lowest_layer_type `lowest_layer_type`]

• 3 / 16
  / 16