Exit Zen
16
string ID 59
type: paragraph
English
Alternatively, a function object may be used. Small function objects will not incur a memory allocation. The follow code declares and sets a function object as a decorator:
172/1720 · 172
16
string ID 89
type: table code
English
HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: upgrade
Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=
Server: Boost.Beast
142/1420 · 142
16
string ID 36
type: table cell
English
The member functions required in `P` should be private. [link beast.ref.boost__beast__rate_policy_access `rate_policy_access`] must be a friend of `P` for the implementation to gain access to the required member functions.
222/2220 · 222
16
string ID 80
type: paragraph
English
struct Body {
13/130 · 13
16
string ID 45
type: table cell
English
A type which meets the requirements of __ConstBufferSequence__. This is the type of buffer returned by `g.prepare(ec)`.
119/1190 · 119
16
string ID 16
type: variablelist cell
English
The server-framework example demonstrates how to implement a server that supports TLS using certificates. There are also websocket and HTTP client examples which use TLS. Furthermore, management of certificates is beyond the scope of the public interfaces of the library. Asio already provides documentation, interfaces, and examples for performing these tasks - Beast does not intend to reinvent them or to redundantly provide this information.
445/4450 · 445
16
string ID 66
type: paragraph
English
The choices for template types must match the message passed on construction. This code creates an HTTP response and the corresponding serializer:
146/1460 · 146
16
string ID 108
type: paragraph
English
Before data can be exchanged, the stream needs to be connected to a peer. The following code sets a timeout for an asynchronous connect operation. In Beast, functions to connect to a range of endpoints (such as the range returned by [@boost:/doc/html/boost_asio/reference/ip__basic_resolver/resolve/overload3.html `net::ip::tcp::resolver::resolve`]) are members of the class rather than free functions such as [@boost:/doc/html/boost_asio/reference/async_connect.html `net::async_connect`].
490/4900 · 490
16
string ID 93
type: paragraph
English
As with most I/O objects, a websocket stream is [*not thread-safe]. Undefined behavior results if two different threads access the object concurrently. For multi-threaded programs, the `tcp_stream` can be constructed from an executor, in this case a strand. The stream declared below will use a strand to invoke all completion handlers:
336/3360 · 336
16
string ID 110
type: heading
English
Auto-fragment
13/130 · 13
16
string ID 114
type: paragraph
English
The example that follows implements a synchronous HTTP relay. It uses a fixed size buffer, to avoid reading in the entire body so that the upstream connection sees a header without unnecessary latency. This example brings together all of the concepts discussed so far, it uses both a __serializer__ and a __parser__ to achieve its goal:
336/3360 · 336
16
string ID 80
type: paragraph
English
If used, the necessary CA certificates must be loaded into the server's SSL context to enable verification of the client's certificate.
135/1350 · 135
16
string ID 44
type: table cell
English
[link beast.ref.boost__beast__saved_handler `saved_handler`]
60/600 · 60
16
string ID 63
type: paragraph
English
Tested with these compilers: msvc-14+, gcc 5.0+, clang 3.6+.
60/600 · 60
16
string ID 46
type: table cell
English
[link beast.ref.boost__beast__get_lowest_layer `get_lowest_layer`]
66/660 · 66
17
string ID 47
type: table cell
English
[link beast.ref.boost__beast__http__chunk_last `chunk_last`]
60/600 · 60
17
string ID 25
type: table cell
English
[path_link example/http/client/coro-ssl/http_client_coro_ssl.cpp http_client_coro_ssl.cpp]
90/900 · 90
17
string ID 21
type: table cell
English
A stream supporting buffer-oriented asynchronous reads and writes.
66/660 · 66
17
string ID 60
type: paragraph
English
This example uses __flat_buffer__. Beast's __basic_parser__ is optimized for structured HTTP data located in a single contiguous (['flat]) memory buffer. When not using a flat buffer the implementation may perform an additional memory allocations to restructure the input into a single buffer for parsing.
305/3050 · 305
110
string ID 110
type: table title
English
Special Fields
14/140 · 14