Exit Zen
4
string ID 34
type: paragraph
English
The __serializer__ automatically applies the chunked transfer encoding when a message returns `true` from [link beast.ref.boost__beast__http__message.chunked.overload1 `message::chunked`]. The boundaries between chunks emitted by the serializer are implementation defined. Chunk extensions and trailers are omitted. Applications which need precise control over the chunk boundaries, extensions, and trailers may use a set of helper classes which enable manual emission of message payloads using chunk encoding.
510/5100 · 510
5
string ID 43
type: paragraph
English
To use these helper classes, first serialize the header portion of the message using the standard interface. Then prepare the buffers, chunk extensions, and desired trailers, and use them with these helpers:
207/2070 · 207
6
string ID 47
type: table title
English
Chunking Helpers
16/160 · 16
9
string ID 47
type: table cell
English
[link beast.ref.boost__beast__http__chunk_body `chunk_body`]
60/600 · 60
10
string ID 47
type: table cell
English
A buffer sequence representing a complete chunk body.
53/530 · 53
11
string ID 47
type: table cell
English
[link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`]
60/600 · 60
12
string ID 47
type: table cell
English
A buffer sequence representing the CRLF (`"\r\n"`) delimiter. This class is used when the caller desires to emit the chunk body in two or more individual stream operations.
172/1720 · 172
13
string ID 47
type: table cell
English
[link beast.ref.boost__beast__http__chunk_extensions `chunk_extensions`]

[link beast.ref.boost__beast__http__basic_chunk_extensions `basic_chunk_extensions`]
158/1580 · 158
14
string ID 47
type: table cell
English
This is a simple, allocating container which lets callers easily build up a set of chunk extensions.
100/1000 · 100
15
string ID 47
type: table cell
English
[link beast.ref.boost__beast__http__chunk_header `chunk_header`]
64/640 · 64
16
string ID 47
type: table cell
English
A buffer sequence representing a hex-encoded chunk size, followed by an optional set of chunk extensions, including the terminating CRLF (`"\r\n"`) delimiter which precedes the chunk body. This class is used when the caller desires to emit the chunk body in two or more individual stream operations.
299/2990 · 299
17
string ID 47
type: table cell
English
[link beast.ref.boost__beast__http__chunk_last `chunk_last`]
60/600 · 60
18
string ID 47
type: table cell
English
A buffer sequence representing a last chunk. The last chunk indicates the end of the chunked message payload, and may contain optional trailer fields.
150/1500 · 150
19
string ID 47
type: table cell
English
[link beast.ref.boost__beast__http__make_chunk `make_chunk`]

[link beast.ref.boost__beast__http__make_chunk_last `make_chunk_last`]
132/1320 · 132
20
string ID 47
type: table cell
English
These helper functions are used to construct a chunk or last chunk directly at call sites.
90/900 · 90
21
string ID 101
type: paragraph
English
We demonstrate the use of these objects first by declaring a function which returns the next buffer sequence to use as a chunk body:
132/1320 · 132
22
string ID 106
type: paragraph
English
This example demonstrates sending a complete chunked message payload manually. No chunk extensions or trailers are emitted:
123/1230 · 123
23
string ID 111
type: paragraph
English
The following code sends additional chunks, and sets chunk extensions using the helper container. The container automatically quotes values in the serialized output when necessary:
180/1800 · 180
24
string ID 117
type: paragraph
English
Callers can take over the generation and management of the extensions buffer by passing a non-owning string. Note that this requires the string contents to adhere to the correct syntax for chunk extensions, including the needed double quotes for values which contain spaces:
274/2740 · 274
25
string ID 124
type: paragraph
English
The next code sample emits a chunked response which promises two trailer fields and delivers them in the last chunk. The implementation allocates memory using the default or a passed-in allocator to hold the state information required to serialize the trailer:
260/2600 · 260