Exit Zen
9
string ID 68
type: paragraph
English
Unlike regular completion handlers used in calls to asynchronous initiation functions, the control callback only needs to be set once. The callback is not reset after being called. The same callback is used for both synchronous and asynchronous reads. The callback is passive; in order to be called, a stream read operation must be active.
339/3390 · 339
9
string ID 59
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]. Handling the Expect field can be implemented easily in a server by constructing a __parser__ to read the header first, then send an informational HTTP response, and finally read the body using the same parser instance. A synchronous version of this server action looks like this:
654/6540 · 654
9
string ID 44
type: table cell
English
This class is designed to be used as a base class when authoring composed asynchronous operations expressed as an intermediate completion handler. This eliminates the need for the extensive boilerplate to propagate the associated executor and the associated allocator.
268/2680 · 268
9
string ID 31
type: paragraph
English
This library is not a client or server, but it can be used to build those things. Many examples are provided, including clients and servers, which may be used as a starting point for writing your own program.
208/2080 · 208
9
string ID 53
type: list
English
* Calling a synchronous function by accident. In general composed
65/650 · 65
9
string ID 19
type: table cell
English
Enables the use of deprecated APIs within Beast.
48/480 · 48
10
string ID 47
type: table cell
English
A buffer sequence representing a complete chunk body.
53/530 · 53
10
string ID 55
type: heading
English
Non-Compliant Peers and Unknown Body Length
43/430 · 43
10
string ID 64
type: list
English
* An intermediate completion handler, called the "composed operation"
69/690 · 69
10
string ID 25
type: table cell
English
[path_link example/http/client/async-ssl/http_client_async_ssl.cpp http_client_async_ssl.cpp]
93/930 · 93
10
string ID 21
type: table cell
English
__SyncStream__
14/140 · 14
10
string ID 16
type: table cell
English
[link beast.ref.boost__beast__http__write.overload1 [*write]]
61/610 · 61
10
string ID 64
type: paragraph
English
Servers send responses, which contain a [@https://tools.ietf.org/html/rfc7231#section-6 status-code], [@https://tools.ietf.org/html/rfc7230#section-3.1.2 reason-phrase], and [@https://tools.ietf.org/html/rfc7230#section-2.6 HTTP-version]. The reason phrase is [@https://tools.ietf.org/html/rfc7230#section-3.1.2 obsolete]: clients SHOULD ignore the reason-phrase content. Here is a response which includes a body. The special [@https://tools.ietf.org/html/rfc7230#section-3.3.2 Content-Length] field informs the remote host of the size of the body which follows.
563/5630 · 563
10
string ID 92
type: paragraph
English
The concepts __ConstBufferSequence__ and __MutableBufferSequence__ describe bidirectional ranges whose value type is convertible to `const_buffer` and `mutable_buffer` respectively. These sequences allow transacting with multiple buffers in a single function call, a technique called [@https://en.wikipedia.org/wiki/Vectored_I/O ['scatter/gather I/O]]. Buffers and buffer sequences are non-owning; copies produce shallow references and not duplicates of the underlying memory. Each of these statements declares a buffer sequence:
529/5290 · 529
10
string ID 25
type: variablelist cell
English
Parsing
7/100 · 7
10
string ID 17
type: table cell
English
[link beast.ref.boost__beast__http__response `response`]
56/560 · 56
10
string ID 55
type: list
English
* [issue 3039] Added `http::basic_fields::contains` member function
* [issue 3050] Removed dependency on Boost.Preprocessor
* [issue 3048] Removed dependency on Boost.StaticAssert
179/1790 · 179
10
string ID 44
type: list
English
* `D` denotes a dynamic buffer class.
* `a` denotes a value of type `D`.
* `c` denotes a (possibly const) value of type `D`.
* `n` denotes a value of type `std::size_t`.
* `T` denotes a type meeting the requirements for __ConstBufferSequence__.
* `U` denotes a type meeting the requirements for __MutableBufferSequence__.
321/3210 · 321
10
string ID 44
type: paragraph
English
is a network programming library previously intended for Boost but not having gone through formal review. As of this writing it still uses the Boost name, namespace, and directory structure although the project states that Boost acceptance is no longer a goal. The library is based on Boost.Asio and bills itself as ['"a collection of network related routines/implementations geared towards providing a robust cross-platform networking library"]. It cites ['"Common Message Type"] as a feature. As of the branch previous linked, it uses these declarations: ``` template <class Tag> struct basic_message {
604/6040 · 604
10
string ID 39
type: table title
English
Valid expressions
17/170 · 17