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

14 string ID 55
	Source string description type: paragraph
	English The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed). 193/1930 · 193 Needs editing (Needs rewriting)
14 string ID 45
	Source string description type: table cell
	English Send a buffer sequence as part of a message.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Send a buffer sequence as part of a message. 44/440 · 44 Needs editing (Needs rewriting)
14 string ID 49
	Source string description type: paragraph
	English This declares a normal function which decorates outgoing HTTP requests:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — This declares a normal function which decorates outgoing HTTP requests: 71/710 · 71 Needs editing (Needs rewriting)
14 string ID 21
	Source string description type: table cell
	English [link beast.ref.boost__beast__buffers_prefix `buffers_prefix`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — [link beast.ref.boost__beast__buffers_prefix `buffers_prefix`] 62/620 · 62 Needs editing (Needs rewriting)
89 string ID 89
	Source string description type: table cell
	English Wire Format
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Wire Format 11/110 · 11 Needs editing (Needs rewriting)
14 string ID 36
	Source string description type: table cell
	English Requires ['MoveConstructible].
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Requires ['MoveConstructible]. 30/300 · 30 Needs editing (Needs rewriting)
14 string ID 66
	Source string description type: heading
	English Value Type
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Value Type 10/100 · 10 Needs editing (Needs rewriting)
14 string ID 45
	Source string description type: table cell
	English Semantics, Pre/Post-conditions
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Semantics, Pre/Post-conditions 30/300 · 30 Needs editing (Needs rewriting)
14 string ID 16
	Source string description type: variablelist cell
	English The name "Boost.Http" or "Boost.WebSocket" would mislead users into believing they could perform an HTTP request on a URL or put up a WebSocket client or server in a couple of lines of code. Where would the core utilities go? Very likely it would step on the owner of Boost.Asio's toes to put things in the boost/asio directory; at the very least, it would create unrequested, additional work for the foreign repository. "Beast" is sufficiently vague as to not suggest any particular functionality, while acting as a memorable umbrella term for a family of low level containers and algorithms. People in the know or with a need for low-level network protocol operations will have no trouble finding it, and the chances of luring a novice into a bad experience are greatly reduced. There is precedent for proper names: "Hana", "Fusion", "Phoenix", and "Spirit" come to mind. Is "Beast" really any worse than say, "mp11" for example? Beast also already has a growing body of users and attention from the open source community, the name Beast comes up in reddit posts and StackOverflow as the answer to questions about which HTTP or WebSocket library to use.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The name "Boost.Http" or "Boost.WebSocket" would mislead users into believing they could perform an HTTP request on a URL or put up a WebSocket client or server in a couple of lines of code. Where would the core utilities go? Very likely it would step on the owner of Boost.Asio's toes to put things in the boost/asio directory; at the very least, it would create unrequested, additional work for the foreign repository. "Beast" is sufficiently vague as to not suggest any particular functionality, while acting as a memorable umbrella term for a family of low level containers and algorithms. People in the know or with a need for low-level network protocol operations will have no trouble finding it, and the chances of luring a novice into a bad experience are greatly reduced. There is precedent for proper names: "Hana", "Fusion", "Phoenix", and "Spirit" come to mind. Is "Beast" really any worse than say, "mp11" for example? Beast also already has a growing body of users and attention from the open source community, the name Beast comes up in reddit posts and StackOverflow as the answer to questions about which HTTP or WebSocket library to use. 1156/11560 · 1156 Needs editing (Needs rewriting)
14 string ID 25
	Source string description type: table cell
	English [link beast.ref.boost__beast__http__response_serializer `response_serializer`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — [link beast.ref.boost__beast__http__response_serializer `response_serializer`] 78/780 · 78 Needs editing (Needs rewriting)
14 string ID 49
	Source string description type: table cell
	English Type
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Type 4/100 · 4 Needs editing (Needs rewriting)
44 string ID 44
	Source string description type: table cell
	English Name
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Name 4/100 · 4 Needs editing (Needs rewriting)
14 string ID 64
	Source string description type: paragraph
	English However, this code is correct:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — However, this code is correct: 30/300 · 30 Needs editing (Needs rewriting)
14 string ID 92
	Source string description type: paragraph
	English 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.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 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. 537/5370 · 537 Needs editing (Needs rewriting)
14 string ID 105
	Source string description type: paragraph
	English However, a problem arises. How do we write a function which can accept an object that is either a request or a response? As written, the only obvious solution is to make the message a template type. Additional traits classes would then be needed to make sure that the passed object has a valid type which meets the requirements. These unnecessary complexities are bypassed by making each container a partial specialization: ``` /// An HTTP message template<bool isRequest, class Fields, class Body> struct message;
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — However, a problem arises. How do we write a function which can accept an object that is either a request or a response? As written, the only obvious solution is to make the message a template type. Additional traits classes would then be needed to make sure that the passed object has a valid type which meets the requirements. These unnecessary complexities are bypassed by making each container a partial specialization: ``` /// An HTTP message template<bool isRequest, class Fields, class Body> struct message; 514/5140 · 514 Needs editing (Needs rewriting)
14 string ID 77
	Source string description type: paragraph
	English When a stream is constructed, any arguments provided to the constructor are forwarded to the next layer object's constructor. This declares a stream over a plain TCP/IP socket using an I/O context:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — When a stream is constructed, any arguments provided to the constructor are forwarded to the next layer object's constructor. This declares a stream over a plain TCP/IP socket using an I/O context: 197/1970 · 197 Needs editing (Needs rewriting)
14 string ID 97
	Source string description type: paragraph
	English When a close frame is received by during a read operation, the implementation will automatically respond with a close frame and then shut down the underlying connection before returning. In this case, the read operation will complete with the code [link beast.ref.boost__beast__websocket__error `error::closed`]. This indicates to the caller that the connection has been closed cleanly.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — When a close frame is received by during a read operation, the implementation will automatically respond with a close frame and then shut down the underlying connection before returning. In this case, the read operation will complete with the code [link beast.ref.boost__beast__websocket__error `error::closed`]. This indicates to the caller that the connection has been closed cleanly. 386/3860 · 386 Needs editing (Needs rewriting)
14 string ID 106
	Source string description type: section title
	English HTTP Relay __example__
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — HTTP Relay __example__ 22/220 · 22 Needs editing (Needs rewriting)
14 string ID 72
	Source string description type: heading
	English Client Certificate
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Client Certificate 18/180 · 18 Needs editing (Needs rewriting)
14 string ID 44
	Source string description type: table cell
	English [link beast.ref.boost__beast__bind_front_handler `bind_front_handler`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — [link beast.ref.boost__beast__bind_front_handler `bind_front_handler`] 70/700 · 70 Needs editing (Needs rewriting)