Exit Zen
7
string ID 44
type: heading
English
User-defined Teardown
21/210 · 21
7
string ID 38
type: table cell
English
Description
11/110 · 11
7
string ID 32
type: list
English
* [link beast.ref.boost__beast__is_buffers_generator `is_buffers_generator`]
* __ConstBufferSequence__
102/1020 · 102
7
string ID 16
type: variablelist cell
English
"There's no HTTP/2 support yet!"
32/320 · 32
7
string ID 25
type: table title
English
Serializer
10/100 · 10
7
string ID 30
type: heading
English
Requirements
12/120 · 12
7
string ID 22
type: table cell
English
This represents configured timeout settings for a websocket stream.
67/670 · 67
7
string ID 34
type: paragraph
English
The example programs that come with the library demonstrate the usage of websocket stream operations with all asynchronous varieties.
133/1330 · 133
7
string ID 54
type: table cell
English
[link beast.ref.boost__beast__tcp_stream `tcp_stream`]
54/540 · 54
7
string ID 46
type: list
English
* `P(x)` is a parsing function which produces a message container from
70/700 · 70
7
string ID 50
type: table title
English
WebSocket Stream Template Parameters
36/360 · 36
7
string ID 33
type: paragraph
English
Establish a WebSocket connection, send a message and receive the reply:
71/710 · 71
7
string ID 46
type: paragraph
English
Ping, pong, and close messages are control frames which may be sent at any time by either peer on an established WebSocket connection. They are sent using the functions [link beast.ref.boost__beast__websocket__stream.ping `ping`], [link beast.ref.boost__beast__websocket__stream.pong `pong`]. and [link beast.ref.boost__beast__websocket__stream.close `close`]. To be notified of control frames, callers may register a ['control callback] using [link beast.ref.boost__beast__websocket__stream.control_callback `control_callback`]. The object provided with this option should be callable with the following signature:
615/6150 · 615
7
string ID 40
type: paragraph
English
The Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Invoking the 100-continue behavior is implemented easily in a client by constructing a __serializer__ to send the header first, then receiving the server response, and finally conditionally send the body using the same serializer instance. A synchronous, simplified version (no timeout) of this client action looks like this:
700/7000 · 700
7
string ID 36
type: paragraph
English
A client must also verify that the hostname or IP address in the certificate matches the expected one. The [@boost:/doc/html/boost_asio/reference/ssl__host_name_verification.html `net::ssl::host_name_verification`] helper function object can perform this verification according to the rules described in RFC 6125:
313/3130 · 313
7
string ID 44
type: table cell
English
Description
11/110 · 11
7
string ID 27
type: list
English
* [*Performance:] Build applications handling thousands of connections or more.
79/790 · 79
7
string ID 48
type: list
English
* Type erasing the final handler. This will cause undefined behavior.
69/690 · 69
7
string ID 19
type: table cell
English
Enables the split compilation mode, which allows the user to compile definitions of non-template entities in a single translation unit, thus improving compilation speed. That translation unit has to include boost/beast/src.hpp in order to compile the definitions.
263/2630 · 263
7
string ID 46
type: table title
English
Layered Stream Algorithms and Types
35/350 · 35