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

8 string ID 42
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * [issue 3042] `http::field` constants are updated. 51/10000 · 51
8 string ID 27
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * `m` is an instance of [link beast.ref.boost__beast__file_mode `file_mode`] * `n` is a number of bytes, convertible to `std::size_t` * `o` is a byte offset in the file, convertible to `std::uint64_t` * `b` is any non-const pointer to memory * `c` is any possibly-const pointer to memory * `ec` is a reference of type [link beast.ref.boost__beast__error_code `error_code`] 372/10000 · 372
8 string ID 29
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A type modeling [*AsyncStream] meets the following requirements: 64/10000 · 64
8 string ID 31
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * `P` denotes a type that meets the requirements of [*RatePolicy]. * `x` denotes an xvalue of type `P` * `a` denotes a value of type `P`. * `n` denotes a value of type `std::size_t` 181/10000 · 181
8 string ID 30
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * `W` denotes a type that meets the requirements of [*FieldsWriter]. * `F` denotes a __Fields__ where 101/10000 · 101
8 string ID 38
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * `boost::asio::is_dynamic_buffer` * __ConstBufferSequence__ * __MutableBufferSequence__ 88/10000 · 88
8 string ID 30
	Source string description type: table title
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Valid expressions 17/10000 · 17
8 string ID 36
	Source string description type: table title
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Valid expressions 17/10000 · 17
8 string ID 33
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — These requirements may undergo non-backward compatible 54/10000 · 54
8 string ID 35
	Source string description type: heading
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Requirements 12/10000 · 12
8 string ID 39
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In this table: 14/10000 · 14
8 string ID 35
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Declarations examples from external libraries have been edited: 63/10000 · 63
8 string ID 16
	Source string description type: variablelist cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Many reviewers feel that HTTP/2 support is an essential feature of a HTTP library. The authors agree that HTTP/2 is important but also feel that the most sensible implementation is one that does not re-use the same network reading and writing interface for 2 as that for 1.0 and 1.1. The Beast HTTP message model was designed with the new protocol in mind and should be evaluated in that context. There are plans to add HTTP/2 in the future, but there is no rush to do so. Users can work with HTTP/1 now; we should not deny them that functionality today to wait for a newer protocol tomorrow. It is the author's position that there is sufficient value in Beast's HTTP/1-only implementation that the lack of HTTP/2 should not be a barrier to acceptance. The Beast HTTP message model is suitable for HTTP/2 and can be re-used. The IETF HTTP Working Group adopted message compatibility with HTTP/1.x as an explicit goal. A parser can simply emit full headers after decoding the compressed HTTP/2 headers. The stream ID is not logically part of the message but rather message metadata and should be communicated out-of-band (see below). HTTP/2 sessions begin with a traditional HTTP/1.1 Upgrade similar in fashion to the WebSocket upgrade. An HTTP/2 implementation can use existing Beast.HTTP primitives to perform this handshake. 1328/10000 · 1328
8 string ID 29
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Beast uses the __DynamicBuffer__ concept presented in the __NetTS__, and relies heavily on the __ConstBufferSequence__ and __MutableBufferSequence__ concepts for passing buffers to functions. The authors have found the dynamic buffer and buffer sequence interfaces to be optimal for interacting with Asio, and for other tasks such as incremental parsing of data in buffers (for example, parsing websocket frames stored in a [link beast.ref.boost__beast__static_buffer `static_buffer`]). 486/10000 · 486
8 string ID 49
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — These relations are true: 25/10000 · 25
8 string ID 35
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — File: [path_link example/websocket/client/sync/websocket_client_sync.cpp websocket_sync_client.cpp] 99/10000 · 99
8 string ID 29
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * [*Basis for Further Abstraction.] Components are well-suited for building upon. 81/10000 · 81
8 string ID 21
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [link beast.ref.boost__beast__buffers_cat `buffers_cat`] 56/10000 · 56
8 string ID 54
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [itemized_list [Timeouts for logical operations] [[@boost:/doc/html/boost_asio/reference/ip__tcp.html `net::ip::tcp`] protocol] [[@boost:/doc/html/boost_asio/reference/executor.html `net::executor`] executor] [[link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`] rate limits] ] 301/10000 · 301
8 string ID 17
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [link beast.ref.boost__beast__file_stdio `file_stdio`] 54/10000 · 54