2. Boost Beast Translation (zh_Hans)
3. English
4. Zen

3 string ID 24
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To enable the implementation to perform the shutdown components of the close operation, the library exposes two customization points expressed as free functions associated with the next layer type: 197/10000 · 197
3 string ID 23
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The boundaries between frames of a multi-frame message are not not considered part of the message. Intermediaries such as proxies which forward the websocket traffic are free to "reframe" (split frames and combine them) the message in arbitrary ways. These intermediaries include Beast, which can reframe messages automatically in some cases depending on the options set on the stream. 385/10000 · 385
3 string ID 18
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A sent ping indicates a request that the sender wants to receive a pong. A pong is a response to a ping. Pongs may be sent unsolicited, at any time. One use for an unsolicited pong is to inform the remote peer that the session is still active after a long period of inactivity. A close frame indicates that the remote peer wishes to close the WebSocket connection. The connection is considered gracefully closed when each side has sent and received a close frame. 463/10000 · 463
3 string ID 21
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To accept incoming connections, an acceptor is used. The websocket stream may be constructed from the socket returned by the acceptor when an incoming connection is established. 177/10000 · 177
3 string ID 18
	Source string description type: section title
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Change Body Type __example__ 28/10000 · 28
4 string ID 15
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — It can be obtained as a string from the `BOOST_BEAST_VERSION` macro or a string through `BOOST_BEAST_VERSION_STRING`. 117/10000 · 117
4 string ID 176
	Source string description type: section title
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Reference 9/10000 · 9
4 string ID 22
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * [issue 3077] Enforced 8KB sanity limit on chunk headers * [issue 3085] Made OpenSSL an optional dependency for tests * [issue 3074] Removed dependency on Boost.StaticAssert * [issue 3091] Added `HTTP2-Settings` to HTTP field enum 231/10000 · 231
4 string ID 16
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * [link beast.ref.boost__beast__file_mode `file_mode`] * [link beast.ref.boost__beast__is_file `is_file`] 105/10000 · 105
4 string ID 20
	Source string description type: heading
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Stream 6/10000 · 6
4 string ID 20
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * [link beast.ref.boost__beast__rate_policy_access `rate_policy_access`] 72/10000 · 72
4 string ID 19
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * __FieldsWriter__ 18/10000 · 18
4 string ID 23
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * A single contiguous octet array, which is reallocated as necessary to 71/10000 · 71
4 string ID 18
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * [link beast.ref.boost__beast__http__is_body `is_body`] * __BodyReader__ * __BodyWriter__ 90/10000 · 90
4 string ID 20
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * [link beast.ref.boost__beast__http__is_fields `is_fields`] * __FieldsWriter__ 79/10000 · 79
4 string ID 23
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * Saving body data to a file 28/10000 · 28
4 string ID 19
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In this way, serializers can be adapted as [*BuffersGenerator], for example [link beast.ref.boost__beast__http__message_generator `http::message_generator`] which provides a type-erased interface for a variety of concrete http message types. 241/10000 · 241
4 string ID 27
	Source string description type: heading
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Associated Types 16/10000 · 16
4 string ID 19
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * Review the message model. Can it represent a complete request or 66/10000 · 66
4 string ID 16
	Source string description type: variablelist cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Beast has a functional HTTP server in the example directory. The server supports both HTTP and WebSocket using synchronous and asynchronous shared or dedicated ports. In addition, the server supports encrypted TLS connections if OpenSSL is available, on dedicated ports. And the server comes with a "multi-port", a flexible single port which supports both encrypted and unencrypted connections, both HTTP and WebSocket, all on the same port. The server is not part of Beast's public interfaces, as that functionality is outside the scope of the library. The author feels that attempting to broaden the scope of the library will reduce its appeal for standardization. 666/10000 · 666