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

18 string ID 66
	Source string description type: table code
	English /// An HTTP header template< bool isRequest, // `true` for requests, `false` for responses class Fields = fields> // The type of container to store the fields class header;
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — /// An HTTP header template< bool isRequest, // `true` for requests, `false` for responses class Fields = fields> // The type of container to store the fields class header; 189/1890 · 189 Needs editing (Needs rewriting)
18 string ID 69
	Source string description type: paragraph
	English The stream operations which work on parsers are:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The stream operations which work on parsers are: 48/480 · 48 Needs editing (Needs rewriting)
18 string ID 94
	Source string description type: list
	English * [issue 2918] Added new examples for Unix domain sockets * [issue 2910] Added SSL/TLS Certificate section to documentation * [issue 2730] Improved documentation of `websocket::stream::async_close`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * [issue 2918] Added new examples for Unix domain sockets * [issue 2910] Added SSL/TLS Certificate section to documentation * [issue 2730] Improved documentation of `websocket::stream::async_close` 197/1970 · 197 Needs editing (Needs rewriting)
18 string ID 30
	Source string description type: table code
	English B::size( B::value_type body)
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — B::size( B::value_type body) 28/280 · 28 Needs editing (Needs rewriting)
18 string ID 34
	Source string description type: table cell
	English Destructible. If `f` refers to an open file, it is first closed as if by a call to `close` with the error ignored.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Destructible. If `f` refers to an open file, it is first closed as if by a call to `close` with the error ignored. 114/1140 · 114 Needs editing (Needs rewriting)
18 string ID 112
	Source string description type: list
	English * The library uses specializations of `string<Tag>` to change the type
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * The library uses specializations of `string<Tag>` to change the type 70/700 · 70 Needs editing (Needs rewriting)
18 string ID 50
	Source string description type: table cell
	English Constructible from `h` and `v`. The lifetime of `h` and `v` are guaranteed to end no earlier than after the `W` is destroyed. The writer shall not access the contents of `h` or `v` before the first call to `init`, permitting lazy construction of the message. The constructor may optionally require that `h` and `v` are `const` references, with these consequences: * If `W` requires that `h` and `v` are const references, then the corresponding serializer constructors for messages with this body type will will accept a const reference to a message, otherwise: * If `W` requires that `h` and `v` are non-const references, then the corresponding serializer constructors for messages with this body type will require a non-const reference to a message.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Constructible from `h` and `v`. The lifetime of `h` and `v` are guaranteed to end no earlier than after the `W` is destroyed. The writer shall not access the contents of `h` or `v` before the first call to `init`, permitting lazy construction of the message. The constructor may optionally require that `h` and `v` are `const` references, with these consequences: * If `W` requires that `h` and `v` are const references, then the corresponding serializer constructors for messages with this body type will will accept a const reference to a message, otherwise: * If `W` requires that `h` and `v` are non-const references, then the corresponding serializer constructors for messages with this body type will require a non-const reference to a message. 753/7530 · 753 Needs editing (Needs rewriting)
18 string ID 36
	Source string description type: table cell
	English `c.get_target_impl()`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — `c.get_target_impl()` 21/210 · 21 Needs editing (Needs rewriting)
18 string ID 84
	Source string description type: paragraph
	English 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:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 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: 195/1950 · 195 Needs editing (Needs rewriting)
18 string ID 71
	Source string description type: table title
	English WebSocket Stream Read Operations
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — WebSocket Stream Read Operations 32/320 · 32 Needs editing (Needs rewriting)
18 string ID 69
	Source string description type: paragraph
	English It also possible for a single decorator to handle both requests and responses, if it is overloaded for both types either as a generic lambda (C++14 and later) or as a class as shown here:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — It also possible for a single decorator to handle both requests and responses, if it is overloaded for both types either as a generic lambda (C++14 and later) or as a class as shown here: 187/1870 · 187 Needs editing (Needs rewriting)
18 string ID 21
	Source string description type: table cell
	English [link beast.ref.boost__beast__buffers_range `buffers_range`] [link beast.ref.boost__beast__buffers_range_ref `buffers_range_ref`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — [link beast.ref.boost__beast__buffers_range `buffers_range`] [link beast.ref.boost__beast__buffers_range_ref `buffers_range_ref`] 129/1290 · 129 Needs editing (Needs rewriting)
18 string ID 106
	Source string description type: paragraph
	English The [link beast.ref.boost__beast__websocket__stream `stream`] member functions [link beast.ref.boost__beast__websocket__stream.accept `accept`] and [link beast.ref.boost__beast__websocket__stream.async_accept `async_accept`] are used to read the WebSocket HTTP Upgrade request handshake from a stream already connected to an incoming peer, and then send the WebSocket HTTP Upgrade response, as shown:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The [link beast.ref.boost__beast__websocket__stream `stream`] member functions [link beast.ref.boost__beast__websocket__stream.accept `accept`] and [link beast.ref.boost__beast__websocket__stream.async_accept `async_accept`] are used to read the WebSocket HTTP Upgrade request handshake from a stream already connected to an incoming peer, and then send the WebSocket HTTP Upgrade response, as shown: 400/4000 · 400 Needs editing (Needs rewriting)
18 string ID 89
	Source string description type: paragraph
	English As long as a suitable reader or writer is available to provide the algorithm for transferring buffers in and out of the value type, those bodies may be parsed or serialized.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — As long as a suitable reader or writer is available to provide the algorithm for transferring buffers in and out of the value type, those bodies may be parsed or serialized. 173/1730 · 173 Needs editing (Needs rewriting)
18 string ID 16
	Source string description type: variablelist cell
	English We presume this means a facility to match expressions against the URI in HTTP requests, and dispatch them to calling code. The authors feel that this is a responsibility of higher level code. Beast does not try to offer a web server. That said, the server-framework example has a concept of request routing called a Service. Two services are provided, one for serving files and the other for handling WebSocket upgrade requests.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — We presume this means a facility to match expressions against the URI in HTTP requests, and dispatch them to calling code. The authors feel that this is a responsibility of higher level code. Beast does not try to offer a web server. That said, the server-framework example has a concept of request routing called a Service. Two services are provided, one for serving files and the other for handling WebSocket upgrade requests. 428/4280 · 428 Needs editing (Needs rewriting)
73 string ID 73
	Source string description type: table title
	English Serializer Stream Operations
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Serializer Stream Operations 28/280 · 28 Needs editing (Needs rewriting)
18 string ID 127
	Source string description type: heading
	English Reading and Writing
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Reading and Writing 19/190 · 19 Needs editing (Needs rewriting)
18 string ID 106
	Source string description type: paragraph
	English The next layer may be accessed by calling [link beast.ref.boost__beast__websocket__stream.next_layer.overload1 `stream::next_layer`].
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The next layer may be accessed by calling [link beast.ref.boost__beast__websocket__stream.next_layer.overload1 `stream::next_layer`]. 133/1330 · 133 Needs editing (Needs rewriting)
18 string ID 128
	Source string description type: paragraph
	English Sometimes it is necessary to send a message whose body is not conveniently described by a single container. For example, when implementing an HTTP relay function a robust implementation needs to present body buffers individually as they become available from the downstream host. These buffers should be fixed in size, otherwise creating the unnecessary and inefficient burden of reading the complete message body before forwarding it to the upstream host.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Sometimes it is necessary to send a message whose body is not conveniently described by a single container. For example, when implementing an HTTP relay function a robust implementation needs to present body buffers individually as they become available from the downstream host. These buffers should be fixed in size, otherwise creating the unnecessary and inefficient burden of reading the complete message body before forwarding it to the upstream host. 457/4570 · 457 Needs editing (Needs rewriting)
18 string ID 87
	Source string description type: paragraph
	English The Subject Alternative Name (SAN) is an extension in X.509 certificates that allows multiple domain names, subdomains, or IP addresses to be associated with a single SSL/TLS certificate. Before that it was the Common Name field in the certificate subject which could contain a single hostname.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The Subject Alternative Name (SAN) is an extension in X.509 certificates that allows multiple domain names, subdomains, or IP addresses to be associated with a single SSL/TLS certificate. Before that it was the Common Name field in the certificate subject which could contain a single hostname. 294/2940 · 294 Needs editing (Needs rewriting)