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

12 string ID 16
	Source string description type: variablelist cell
	English The energy invested in Beast went into the design of the interfaces, not performance. That said, the most sensitive parts of Beast have been optimized or designed with optimization in mind. The slow parts of WebSocket processing have been optimized, and the HTTP parser design is lifted from another extremely popular project which has performance as a design goal (see [@https://github.com/h2o/picohttpparser]). From: [@http://www.boost.org/development/requirements.html] "Aim first for clarity and correctness; optimization should be only a secondary concern in most Boost libraries." As the library matures it will undergo optimization passes; benchmarks will logically accompany this process. There is a small benchmarking program included in the tests which compares the performance of Beast's parser to the NodeJS reference parser, as well as some benchmarks which compare the performance of various Beast dynamic buffer implementations against Asio's.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The energy invested in Beast went into the design of the interfaces, not performance. That said, the most sensitive parts of Beast have been optimized or designed with optimization in mind. The slow parts of WebSocket processing have been optimized, and the HTTP parser design is lifted from another extremely popular project which has performance as a design goal (see [@https://github.com/h2o/picohttpparser]). From: [@http://www.boost.org/development/requirements.html] "Aim first for clarity and correctness; optimization should be only a secondary concern in most Boost libraries." As the library matures it will undergo optimization passes; benchmarks will logically accompany this process. There is a small benchmarking program included in the tests which compares the performance of Beast's parser to the NodeJS reference parser, as well as some benchmarks which compare the performance of various Beast dynamic buffer implementations against Asio's. 961/9610 · 961 Needs editing (Needs rewriting)
12 string ID 25
	Source string description type: table cell
	English [link beast.ref.boost__beast__http__request_serializer `request_serializer`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — [link beast.ref.boost__beast__http__request_serializer `request_serializer`] 76/760 · 76 Needs editing (Needs rewriting)
12 string ID 49
	Source string description type: table title
	English Valid expressions
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Valid expressions 17/170 · 17 Needs editing (Needs rewriting)
12 string ID 42
	Source string description type: paragraph
	English There are three timeout settings which may be set independently on the stream:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — There are three timeout settings which may be set independently on the stream: 78/780 · 78 Needs editing (Needs rewriting)
12 string ID 54
	Source string description type: list
	English * [link beast.ref.boost__beast__websocket__stream.async_read `async_read`] or [link beast.ref.boost__beast__websocket__stream.async_read_some `async_read_some`] * [link beast.ref.boost__beast__websocket__stream.async_write `async_write`] or [link beast.ref.boost__beast__websocket__stream.async_write_some `async_write_some`] * [link beast.ref.boost__beast__websocket__stream.async_ping `async_ping`] or [link beast.ref.boost__beast__websocket__stream.async_pong `async_pong`] * [link beast.ref.boost__beast__websocket__stream.async_close `async_close`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * [link beast.ref.boost__beast__websocket__stream.async_read `async_read`] or [link beast.ref.boost__beast__websocket__stream.async_read_some `async_read_some`] * [link beast.ref.boost__beast__websocket__stream.async_write `async_write`] or [link beast.ref.boost__beast__websocket__stream.async_write_some `async_write_some`] * [link beast.ref.boost__beast__websocket__stream.async_ping `async_ping`] or [link beast.ref.boost__beast__websocket__stream.async_pong `async_pong`] * [link beast.ref.boost__beast__websocket__stream.async_close `async_close`] 553/5530 · 553 Needs editing (Needs rewriting)
12 string ID 78
	Source string description type: paragraph
	English 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:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 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: 499/4990 · 499 Needs editing (Needs rewriting)
12 string ID 63
	Source string description type: paragraph
	English Here is our first attempt at declaring some message containers:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Here is our first attempt at declaring some message containers: 63/630 · 63 Needs editing (Needs rewriting)
12 string ID 50
	Source string description type: table cell
	English `deflateSupported`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — `deflateSupported` 18/180 · 18 Needs editing (Needs rewriting)
12 string ID 83
	Source string description type: paragraph
	English The WebSocket protocol defines a procedure and control message for initiating a close of the session. In this procedure, a host requests the close by sending a [@https://tools.ietf.org/html/rfc6455#section-5.5.1 ['close frame]]. To request a close use a close function such as [link beast.ref.boost__beast__websocket__stream.close.overload2 `close`] or [link beast.ref.boost__beast__websocket__stream.async_close `async_close`]:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The WebSocket protocol defines a procedure and control message for initiating a close of the session. In this procedure, a host requests the close by sending a [@https://tools.ietf.org/html/rfc6455#section-5.5.1 ['close frame]]. To request a close use a close function such as [link beast.ref.boost__beast__websocket__stream.close.overload2 `close`] or [link beast.ref.boost__beast__websocket__stream.async_close `async_close`]: 428/4280 · 428 Needs editing (Needs rewriting)
12 string ID 93
	Source string description type: section title
	English HEAD response (Server) __example__
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — HEAD response (Server) __example__ 34/340 · 34 Needs editing (Needs rewriting)
12 string ID 62
	Source string description type: paragraph
	English The following Boost.Asio methods can be used for loading a certificate or a certificate chain:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The following Boost.Asio methods can be used for loading a certificate or a certificate chain: 94/940 · 94 Needs editing (Needs rewriting)
12 string ID 44
	Source string description type: table cell
	English [link beast.ref.boost__beast__bind_handler `bind_handler`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — [link beast.ref.boost__beast__bind_handler `bind_handler`] 58/580 · 58 Needs editing (Needs rewriting)
12 string ID 49
	Source string description type: section title
	English Requirements
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Requirements 12/120 · 12 Needs editing (Needs rewriting)
12 string ID 68
	Source string description type: list
	English * For operations which complete immediately (i.e. without calling an
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * For operations which complete immediately (i.e. without calling an 68/680 · 68 Needs editing (Needs rewriting)
12 string ID 46
	Source string description type: table cell
	English [link beast.ref.boost__beast__buffered_read_stream `buffered_read_stream`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — [link beast.ref.boost__beast__buffered_read_stream `buffered_read_stream`] 74/740 · 74 Needs editing (Needs rewriting)
13 string ID 47
	Source string description type: table cell
	English [link beast.ref.boost__beast__http__chunk_extensions `chunk_extensions`] [link beast.ref.boost__beast__http__basic_chunk_extensions `basic_chunk_extensions`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — [link beast.ref.boost__beast__http__chunk_extensions `chunk_extensions`] [link beast.ref.boost__beast__http__basic_chunk_extensions `basic_chunk_extensions`] 158/1580 · 158 Needs editing (Needs rewriting)
13 string ID 79
	Source string description type: paragraph
	English The initiating function definition itself is straightforward. We perform type checking on the parameters, and then let `net::async_initiate` capture the parameter list along with a copy of our initiation function object. Depending on the specialization of `async_result` for the type of `CompletionToken`, the initiation function may be invoked immediately. Alternatively, it may be invoked later, after the initiating function returns. This is known as "lazy execution," and allows efficient and expressive abstractions to be written.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The initiating function definition itself is straightforward. We perform type checking on the parameters, and then let `net::async_initiate` capture the parameter list along with a copy of our initiation function object. Depending on the specialization of `async_result` for the type of `CompletionToken`, the initiation function may be invoked immediately. Alternatively, it may be invoked later, after the initiating function returns. This is known as "lazy execution," and allows efficient and expressive abstractions to be written. 535/5350 · 535 Needs editing (Needs rewriting)
13 string ID 25
	Source string description type: table cell
	English HTTP, asynchronous using __system_executor__
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — HTTP, asynchronous using __system_executor__ 44/440 · 44 Needs editing (Needs rewriting)
13 string ID 21
	Source string description type: table cell
	English Supports buffer-oriented asynchronous reads.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Supports buffer-oriented asynchronous reads. 44/440 · 44 Needs editing (Needs rewriting)
13 string ID 16
	Source string description type: table cell
	English Write a __message__ to an __AsyncWriteStream__.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Write a __message__ to an __AsyncWriteStream__. 47/470 · 47 Needs editing (Needs rewriting)