Exit Zen
26
string ID 111
type: paragraph
English
The __DynamicBuffer__ concept introduced in __Asio__ models a buffer sequence which supports an owning, resizable range. Beast provides this set of additional implementations of the dynamic buffer concept:
205/2050 · 205
26
string ID 155
type: paragraph
English
The WebSocket protocol understands the concept of subprotocols. If the client is requesting one of a set of subprotocols it will set the header [@https://tools.ietf.org/html/rfc6455#section-11.3.4 Sec-WebSocket-Protocol] in the initial WebSocket Upgrade HTTP request. It is up to the server to parse the header and select one of the protocols to accept. The server indicates the selected protocol by setting the [@https://tools.ietf.org/html/rfc6455#section-11.3.4 Sec-WebSocket-Protocol] header in the accept header.
517/5170 · 517
26
string ID 139
type: paragraph
English
Finally, here is the implementation of the reader member functions:
67/670 · 67
26
string ID 45
type: table cell
English
An alias for `std::true_type` for `G`, otherwise an alias for `std::false_type`.
80/800 · 80
26
string ID 16
type: variablelist cell
English
Deciding on whether to send the "Expect: 100-continue" header or how to handle it on the server side is the caller's responsibility; Beast provides the functionality to send or inspect the header before sending or reading the body.
231/2310 · 231
26
string ID 73
type: table cell
English
Send only the header from a __serializer__ to a __SyncWriteStream__.
68/680 · 68
26
string ID 49
type: table cell
English
`std::true_type`
16/160 · 16
26
string ID 84
type: paragraph
English
For manual control over the settings, a timeout options object may be constructed. Here we enable only the handshake timeout.
125/1250 · 125
26
string ID 180
type: paragraph
English
The [link beast.ref.boost__beast__basic_stream `basic_stream`] class template supports an additional `RatePolicy` template parameter. Objects of this type must meet the requirements of __RatePolicy__. They are used to implement rate limiting or bandwidth management. The default policy for `basic_stream` and `tcp_stream` is [link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`], which places no limits on reading and writing. The library comes with the [link beast.ref.boost__beast__simple_rate_policy `simple_rate_policy`], allowing for independent control of read and write limits expressed in terms of bytes per second. The follow code creates an instance of the basic stream with a simple rate policy, and sets the read and write limits:
765/7650 · 765
26
string ID 121
type: paragraph
English
A self-issued certificate is a certificate where the issuer and subject are the same entity.
92/920 · 92
26
string ID 132
type: paragraph
English
Thanks to [@https://github.com/djarek Damian Jarek] for his generous participation and source code contributions.
113/1130 · 113
27
string ID 135
type: paragraph
English
Alternatively, callers can take over the generation and lifetime management of the serialized trailer fields by passing in a non-owning string:
143/1430 · 143
27
string ID 68
type: paragraph
English
These WebSocket clients connect to a server and send a message, then receive a message and print the response before disconnecting. All asynchronous clients support timeouts.
174/1740 · 174
27
string ID 63
type: table cell
English
Determine if a type meets the requirements of __AsyncReadStream__.
66/660 · 66
27
string ID 110
type: table cell
English
The Upgrade header field provides a mechanism to transition from HTTP/1.1 to another protocol on the same connection. For example, it is the mechanism used by WebSocket's initial HTTP handshake to establish a WebSocket connection.
230/2300 · 230
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
27
string ID 120
type: table cell
English
A body whose [link beast.ref.boost__beast__http__buffer_body__value_type `value_type`] holds a raw pointer and size to a caller-provided buffer. This allows for serialization of body data coming from external sources, and incremental parsing of message body content using a fixed size buffer.
292/2920 · 292
27
string ID 71
type: table cell
English
Read only the header octets into a parser from a __SyncReadStream__.
68/680 · 68
27
string ID 153
type: list
English
* [issue 2875] `ssl_stream` and `flat_stream` marked as deprecated
* [issue 2875] `net::ssl::stream` is canonical in snippets and examples
* [issue 2872] Added `SSL/TLS Shutdown Procedure` section
196/1960 · 196
27
string ID 51
type: table cell
English
Returns the maximum sum of the sizes of the input sequence and output sequence that the dynamic buffer can hold without requiring reallocation.
143/1430 · 143