Exit Zen
11
string ID 45
type: table title
English
Valid expressions
17/170 · 17
11
string ID 16
type: variablelist cell
English
"You need benchmarks!"
22/220 · 22
11
string ID 25
type: table code
English
/// Provides buffer oriented HTTP message serialization functionality.
template<
bool isRequest,
class Body,
class Fields = fields
>
class serializer;
150/1500 · 150
11
string ID 42
type: list
English
* `a` denotes a value of type `R`.
* `b` is an object whose type meets the requirements of __ConstBufferSequence__
* `h` denotes a value of type `header<isRequest, Fields>&`.
* `v` denotes a value of type `Body::value_type&`.
* `n` is a value of type `boost::optional<std::uint64_t>`.
* `ec` is a value of type [link beast.ref.boost__beast__error_code `error_code&`].
367/3670 · 367
11
string ID 22
type: table cell
English
This function sets timeout and other options on the stream.
59/590 · 59
11
string ID 47
type: paragraph
English
Like a regular __Asio__ socket, a [link beast.ref.boost__beast__websocket__stream `stream`] is not thread safe. Callers are responsible for synchronizing operations on the socket using an implicit or explicit strand, as per the Asio documentation. The websocket stream asynchronous interface supports one of each of the following operations to be active at the same time:
371/3710 · 371
11
string ID 76
type: heading
English
Construction
12/120 · 12
11
string ID 55
type: paragraph
English
We would also like our message container to have customization points permitting the following: allocator awareness, user-defined containers to represent header fields, and user-defined types and algorithms to represent the body. And finally, because requests and responses have different fields in the ['start-line], we would like the containers for requests and responses to be represented by different types for function overloading.
436/4360 · 436
11
string ID 50
type: table cell
English
The type of the next layer. An object of this type will be constructed and maintained for the lifetime of the stream. All reads and writes will go through the next layer. This type must meet the requirements of either __SyncStream__, __AsyncStream__, or both, depending on the style of I/O that is to be performed.
314/3140 · 314
11
string ID 81
type: heading
English
Close Frames
12/120 · 12
11
string ID 77
type: paragraph
English
The [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request] method indicates to the server that the client wishes to receive the entire header that would be delivered if the method was GET, except that the body is omitted. When a client wishes to receive the response to a HEAD request, it is necessary to inform the parser not to expect a body. This is done by calling [link beast.ref.boost__beast__http__basic_parser.skip `basic_parser::skip`] with the value `true`, as shown in this example:
504/5040 · 504
11
string ID 57
type: paragraph
English
When a server certificate is issued by an intermediate certificate authority, and the client lacks those intermediate certificates, the server should provide all the relevant certificates to the client. This allows the client to verify the final certificate in the chain against the root certificate.
300/3000 · 300
11
string ID 44
type: table cell
English
For composed operation algorithms which need stable storage for temporary objects, this function may be used. Memory for the stable storage is allocated using the allocator associated with the final completion handler. The implementation automatically destroys the temporary object before the final completion handler is invoked, or when the intermediate completion handler is destroyed.
387/3870 · 387
11
string ID 37
type: paragraph
English
Beast empowers users to create their own libraries, clients, and servers using HTTP/1 and WebSocket. Code will be easier and faster to implement, understand, and maintain, because Beast takes care of the low-level protocol details. The HTTP and WebSocket protocols drive most of the World Wide Web. Every web browser implements these protocols to load webpages and to enable client side programs (often written in JavaScript) to communicate interactively. C++ benefits greatly from having a standardized implementation of these protocols.
538/5380 · 538
11
string ID 65
type: list
English
* Forgetting to create an object of type __executor_work_guard__ with the
73/730 · 73
11
string ID 19
type: table cell
English
Sets the small buffer size for the file_body. Defaults to 4096.
63/630 · 63
11
string ID 46
type: table cell
English
This stream can be used for synchronous and asynchronous reading and writing. It allows timeouts to be set on logical operations, and can have an executor associated with the stream which is used to invoke completion handlers. This lets you set a strand on the stream once, which is then used for all asynchronous operations automatically.
339/3390 · 339
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
12
string ID 63
type: paragraph
English
The following is an example that can read an HTTP response from such a server:
78/780 · 78
12
string ID 73
type: paragraph
English
Here we forward declare the composed operation type, and provide the definition of the initiation function object. They are placed in the `detail` namespace since they should not be public:
189/1890 · 189