2. Boost Beast Translation (zh_Hans)
3. Doc / Qbk / 04 Http / 05 Parser Streams (qbk)
4. English
5. Zen

27 string ID 71
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Read only the header octets into a parser from a __SyncReadStream__. 68/10000 · 68
28 string ID 71
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [link beast.ref.boost__beast__http__async_read_header [*async_read_header]] 75/10000 · 75
29 string ID 71
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Read only the header octets into a parser asynchronously from an __AsyncReadStream__. 85/10000 · 85
30 string ID 71
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [link beast.ref.boost__beast__http__read_some.overload1 [*read_some]] 69/10000 · 69
31 string ID 71
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Read some octets into a parser from a __SyncReadStream__. 57/10000 · 57
32 string ID 71
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — [link beast.ref.boost__beast__http__async_read_some [*async_read_some]] 71/10000 · 71
33 string ID 71
	Source string description type: table cell
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Read some octets into a parser asynchronously from an __AsyncReadStream__. 74/10000 · 74
34 string ID 105
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — As with message stream operations, parser stream operations require a persisted __DynamicBuffer__ for holding unused octets from the stream. The basic parser implementation is optimized for the case where this dynamic buffer stores its input sequence in a single contiguous memory buffer. It is advised to use an instance of __flat_buffer__, __flat_static_buffer__, or __flat_static_buffer_base__ for this purpose, although a user defined instance of __DynamicBuffer__ which produces input sequences of length one is also suitable. 532/10000 · 532
35 string ID 114
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The parser contains a message constructed internally. Arguments passed to the parser's constructor are forwarded into the message container. The caller can access the message inside the parser by calling [link beast.ref.boost__beast__http__parser.get `parser::get`]. If the `Fields` and `Body` types are [*MoveConstructible], the caller can take ownership of the message by calling [link beast.ref.boost__beast__http__parser.release `parser::release`]. In this example we read an HTTP response with a string body using a parser, then print the response: 553/10000 · 553
36 string ID 128
	Source string description type: section title
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Incremental Read __example__ 28/10000 · 28
37 string ID 130
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This function uses [link beast.ref.boost__beast__http__buffer_body `buffer_body`] and parser stream operations to read a message body progressively using a small, fixed-size buffer: 181/10000 · 181
38 string ID 141
	Source string description type: section title
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Reading large response body __example__ 39/10000 · 39
39 string ID 143
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This example presents how to increase the default limit of the response body size, thus the content larger than the default 8MB can be read. 140/10000 · 140
The translation has come to an end.