The translation has come to an end.
Exit Zen
26
string ID 80
type: table cell
English
[@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked-body]]
66/660 · 66
27
string ID 80
type: table cell
English
Until now parse and serialize operations apply or remove the chunked transfer coding as needed for message payloads whose size is not known ahead of time. For some domain specific niches, it is necessary to assume direct control over incoming or outgoing chunks in a chunk encoded message payload. For parsing this is achieved by setting hooks using the functions [link beast.ref.boost__beast__http__parser.on_chunk_header `on_chunk_header`] and/or [link beast.ref.boost__beast__http__parser.on_chunk_body `on_chunk_body`]. For serializing callers may first emit the header, and then use these buffer sequence adapters to control the contents of each chunk including [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk extensions]] and the [@https://tools.ietf.org/html/rfc7230#section-4.1.2 ['trailer-part]]: [link beast.ref.boost__beast__http__chunk_body `chunk_body`], [link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`], [link beast.ref.boost__beast__http__chunk_header `chunk_header`], and [link beast.ref.boost__beast__http__chunk_last `chunk_last`].
1073/10730 · 1073
28
string ID 80
type: table cell
English
[*1]
4/100 · 4
29
string ID 80
type: table cell
English
buffers
7/100 · 7
30
string ID 80
type: table cell
English
For ultimate control, the use of library stream algorithms may be bypassed entirely and instead work directly with buffers by calling members of __parser__ or __serializer__.
174/1740 · 174
31
string ID 80
type: table cell
English
[*0]
4/100 · 4
32
string ID 80
type: table cell
English
['user-defined]
15/150 · 15
33
string ID 80
type: table cell
English
In addition to the typical customization points of __Stream__ and __DynamicBuffer__, user-defined types may replace parts of the library implementation at the lowest level. The customization points include __Fields__ for creating a container to store HTTP fields, __Body__ for defining containers and algorithms used for HTTP message payloads, and user-defined subclasses of __basic_parser__ for implementing custom message representation strategies.
450/4500 · 450
34
string ID 193
type: paragraph
English
This documentation assumes some familiarity with __Asio__ and
61/610 · 61
The translation has come to an end.