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

22 string ID 45
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `g.consume(n)` 14/10000 · 14
22 string ID 50
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — `W<W::const_buffers_type>` 26/10000 · 26
22 string ID 140
	Source string description type: heading
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Boost.HTTP 10/10000 · 10
22 string ID 16
	Source string description type: variablelist cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Beast works with the Stream concept, so it automatically works with the `boost::asio::ssl::stream` that you have already set up through Asio. 141/10000 · 141
22 string ID 165
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Often, in non-trivial HTTP applications, we want to read the HTTP header and examine its contents before choosing a type for [*Body]. To accomplish this, there needs to be a way to model the header portion of a message. And we'd like to do this in a way that allows functions which take the header as a parameter, to also accept a type representing the whole message (the function will see just the header part). This suggests inheritance, by splitting a new base class off of the message: ``` /// An HTTP message header template<bool isRequest, class Fields> struct header; ``` 578/10000 · 578
22 string ID 91
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — To report bugs or get help using Beast, GitHub issues are preferred. Please visit [@https://github.com/boostorg/beast/issues https://github.com/boostorg/beast/issues] to ask a question, report a defect, or request a feature. If you prefer to keep your issue or question confidential please email the author at [@mailto:vinnie.falco%40gmail.com vinnie.falco@gmail.com]. 368/10000 · 368
22 string ID 21
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [link beast.ref.boost__beast__buffers_to_string `buffers_to_string`] 68/10000 · 68
22 string ID 155
	Source string description type: heading
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https_get 9/10000 · 9
22 string ID 105
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The following Boost.Asio methods can be used for loading a private key: 71/10000 · 71
22 string ID 105
	Source string description type: section title
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Counted Stream __example__ 26/10000 · 26
22 string ID 229
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The allocator is used by the implementation to obtain any temporary storage necessary to perform the operation. Temporary allocations are always freed before the completion handler is invoked. The executor is a cheaply copyable object providing the algorithm used to invoke the completion handler. Unless customized by the caller, a completion handler defaults to using `std::allocator<void>` and the executor of the corresponding I/O object. 442/10000 · 442
22 string ID 63
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [link beast.ref.boost__beast__executor_type `executor_type`] 60/10000 · 60
22 string ID 25
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [path_link example/http/client/crawl/http_crawl.cpp http_crawl.cpp] 67/10000 · 67
22 string ID 110
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [@https://tools.ietf.org/html/rfc7230#section-3.3.2 [*`Content-Length`]] 72/10000 · 72
22 string ID 80
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [*3] 4/10000 · 4
22 string ID 66
	Source string description type: table code
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — /// A typical HTTP response header template<class Fields> using response_header = header<false, Fields>; 104/10000 · 104
22 string ID 71
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [link beast.ref.boost__beast__http__read.overload1 [*read]] 59/10000 · 59
22 string ID 106
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This example demonstrates sending a complete chunked message payload manually. No chunk extensions or trailers are emitted: 123/10000 · 123
22 string ID 97
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A set of free functions allow serialization of an entire HTTP message to a stream. This example constructs and sends an HTTP response: 134/10000 · 134
22 string ID 99
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parsing from a `std::istream` could be implemented using an alternate 69/10000 · 69