2. Boost Beast Translation (zh_Hans)
3. Chinese (Simplified Han script)
4. Zen

26 string ID 49
	Source string description type: table cell
	English `std::true_type`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — `std::true_type` 16/160 · 16 Needs editing (Needs rewriting)
26 string ID 84
	Source string description type: paragraph
	English For manual control over the settings, a timeout options object may be constructed. Here we enable only the handshake timeout.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — For manual control over the settings, a timeout options object may be constructed. Here we enable only the handshake timeout. 125/1250 · 125 Needs editing (Needs rewriting)
26 string ID 180
	Source string description type: paragraph
	English 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:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 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: 765/7650 · 765 Needs editing (Needs rewriting)
201 string ID 201
	Source string description type: paragraph
	English };
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — }; 2/100 · 2 Needs editing (Needs rewriting)
26 string ID 121
	Source string description type: paragraph
	English A self-issued certificate is a certificate where the issuer and subject are the same entity.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — A self-issued certificate is a certificate where the issuer and subject are the same entity. 92/920 · 92 Needs editing (Needs rewriting)
26 string ID 132
	Source string description type: paragraph
	English Thanks to [@https://github.com/djarek Damian Jarek] for his generous participation and source code contributions.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Thanks to [@https://github.com/djarek Damian Jarek] for his generous participation and source code contributions. 113/1130 · 113 Needs editing (Needs rewriting)
27 string ID 135
	Source string description type: paragraph
	English Alternatively, callers can take over the generation and lifetime management of the serialized trailer fields by passing in a non-owning string:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Alternatively, callers can take over the generation and lifetime management of the serialized trailer fields by passing in a non-owning string: 143/1430 · 143 Needs editing (Needs rewriting)
27 string ID 68
	Source string description type: paragraph
	English These WebSocket clients connect to a server and send a message, then receive a message and print the response before disconnecting. All asynchronous clients support timeouts.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — These WebSocket clients connect to a server and send a message, then receive a message and print the response before disconnecting. All asynchronous clients support timeouts. 174/1740 · 174 Needs editing (Needs rewriting)
27 string ID 63
	Source string description type: table cell
	English Determine if a type meets the requirements of __AsyncReadStream__.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Determine if a type meets the requirements of __AsyncReadStream__. 66/660 · 66 Needs editing (Needs rewriting)
27 string ID 110
	Source string description type: table cell
	English The Upgrade header field provides a mechanism to transition from HTTP/1.1 to another protocol on the same connection. For example, it is the mechanism used by WebSocket's initial HTTP handshake to establish a WebSocket connection.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The Upgrade header field provides a mechanism to transition from HTTP/1.1 to another protocol on the same connection. For example, it is the mechanism used by WebSocket's initial HTTP handshake to establish a WebSocket connection. 230/2300 · 230 Needs editing (Needs rewriting)
27 string ID 254
	Source string description type: list
	English # `partial`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — # `partial` 11/110 · 11 Needs editing (Needs rewriting)
27 string ID 80
	Source string description type: table cell
	English Until now parse and serialize operations apply or remove the chunked transfer coding as needed for message payloads whose size is not known ahead of time. For some domain specific niches, it is necessary to assume direct control over incoming or outgoing chunks in a chunk encoded message payload. For parsing this is achieved by setting hooks using the functions [link beast.ref.boost__beast__http__parser.on_chunk_header `on_chunk_header`] and/or [link beast.ref.boost__beast__http__parser.on_chunk_body `on_chunk_body`]. For serializing callers may first emit the header, and then use these buffer sequence adapters to control the contents of each chunk including [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk extensions]] and the [@https://tools.ietf.org/html/rfc7230#section-4.1.2 ['trailer-part]]: [link beast.ref.boost__beast__http__chunk_body `chunk_body`], [link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`], [link beast.ref.boost__beast__http__chunk_header `chunk_header`], and [link beast.ref.boost__beast__http__chunk_last `chunk_last`].
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Until now parse and serialize operations apply or remove the chunked transfer coding as needed for message payloads whose size is not known ahead of time. For some domain specific niches, it is necessary to assume direct control over incoming or outgoing chunks in a chunk encoded message payload. For parsing this is achieved by setting hooks using the functions [link beast.ref.boost__beast__http__parser.on_chunk_header `on_chunk_header`] and/or [link beast.ref.boost__beast__http__parser.on_chunk_body `on_chunk_body`]. For serializing callers may first emit the header, and then use these buffer sequence adapters to control the contents of each chunk including [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk extensions]] and the [@https://tools.ietf.org/html/rfc7230#section-4.1.2 ['trailer-part]]: [link beast.ref.boost__beast__http__chunk_body `chunk_body`], [link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`], [link beast.ref.boost__beast__http__chunk_header `chunk_header`], and [link beast.ref.boost__beast__http__chunk_last `chunk_last`]. 1073/10730 · 1073 Needs editing (Needs rewriting)
27 string ID 120
	Source string description type: table cell
	English A body whose [link beast.ref.boost__beast__http__buffer_body__value_type `value_type`] holds a raw pointer and size to a caller-provided buffer. This allows for serialization of body data coming from external sources, and incremental parsing of message body content using a fixed size buffer.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — A body whose [link beast.ref.boost__beast__http__buffer_body__value_type `value_type`] holds a raw pointer and size to a caller-provided buffer. This allows for serialization of body data coming from external sources, and incremental parsing of message body content using a fixed size buffer. 292/2920 · 292 Needs editing (Needs rewriting)
27 string ID 71
	Source string description type: table cell
	English Read only the header octets into a parser from a __SyncReadStream__.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Read only the header octets into a parser from a __SyncReadStream__. 68/680 · 68 Needs editing (Needs rewriting)
27 string ID 153
	Source string description type: list
	English * [issue 2875] `ssl_stream` and `flat_stream` marked as deprecated * [issue 2875] `net::ssl::stream` is canonical in snippets and examples * [issue 2872] Added `SSL/TLS Shutdown Procedure` section
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * [issue 2875] `ssl_stream` and `flat_stream` marked as deprecated * [issue 2875] `net::ssl::stream` is canonical in snippets and examples * [issue 2872] Added `SSL/TLS Shutdown Procedure` section 196/1960 · 196 Needs editing (Needs rewriting)
27 string ID 51
	Source string description type: table cell
	English Returns the maximum sum of the sizes of the input sequence and output sequence that the dynamic buffer can hold without requiring reallocation.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Returns the maximum sum of the sizes of the input sequence and output sequence that the dynamic buffer can hold without requiring reallocation. 143/1430 · 143 Needs editing (Needs rewriting)
34 string ID 34
	Source string description type: table cell
	English `std::uint64_t`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 0/150 · 15 Needs editing
27 string ID 174
	Source string description type: paragraph
	English template<class Headers, class Body> struct is_message<basic_message<Headers, Body>>: public std::true_type {}; ```
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — template<class Headers, class Body> struct is_message<basic_message<Headers, Body>>: public std::true_type {}; ``` 114/1140 · 114 Needs editing (Needs rewriting)
27 string ID 36
	Source string description type: table cell
	English `c.has_content_length()`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — `c.has_content_length()` 24/240 · 24 Needs editing (Needs rewriting)
27 string ID 96
	Source string description type: paragraph
	English After the WebSocket handshake is accomplished, callers may send and receive messages using the message oriented interface. This interface requires that all of the buffers representing the message are known ahead of time:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — After the WebSocket handshake is accomplished, callers may send and receive messages using the message oriented interface. This interface requires that all of the buffers representing the message are known ahead of time: 220/2200 · 220 Needs editing (Needs rewriting)