Exit Zen
25
string ID 25
type: table cell
English
HTTP, asynchronous Unix domain sockets
38/380 · 38
11
string ID 21
type: table cell
English
A stream supporting buffer-oriented blocking reads and writes.
62/620 · 62
11
string ID 16
type: table cell
English
Write a __message__ to a __SyncWriteStream__.
45/450 · 45
11
string ID 75
type: table code
English
HTTP/1.1 200 OK\r\n
Server: Beast\r\n
Content-Length: 13\r\n
\r\n
Hello, world!
79/790 · 79
11
string ID 104
type: paragraph
English
The functions [@boost:/doc/html/boost_asio/reference/buffer_size.html `net::buffer_size`] and [@boost:/doc/html/boost_asio/reference/buffer_copy.html `net::buffer_copy`] determine the total number of bytes in a buffer sequence, and transfer some or all of bytes from one buffer sequence to another respectively. The function `buffer_size` is a customization point: user defined overloads in foreign namespaces are possible, and callers should invoke `buffer_size` without namespace qualification. The functions [@boost:/doc/html/boost_asio/reference/buffer_sequence_begin.html `net::buffer_sequence_begin`] and [@boost:/doc/html/boost_asio/reference/buffer_sequence_end.html `net::buffer_sequence_end`] are used to obtain a pair of iterators for traversing the sequence. Beast provides a set of buffer sequence types and algorithms such as [link beast.ref.boost__beast__buffers_cat `buffers_cat`], [link beast.ref.boost__beast__buffers_front `buffers_front`], [link beast.ref.boost__beast__buffers_prefix `buffers_prefix`], [link beast.ref.boost__beast__buffers_range `buffers_range`], and [link beast.ref.boost__beast__buffers_suffix `buffers_suffix`]. This example returns the bytes in a buffer sequence as a string:
1218/12180 · 1218
11
string ID 25
type: variablelist cell
English
The __parser__ attempts to convert a series of octet buffers into a __message__.
80/800 · 80
11
string ID 17
type: table code
English
/// A typical HTTP response
template<class Body, class Fields = fields>
using response = message<false, Body, Fields>;
118/1180 · 118
11
string ID 29
type: table cell
English
__parser__
10/100 · 10
11
string ID 59
type: heading
English
Boost 1.89
10/100 · 10
11
string ID 51
type: table title
English
Valid expressions
17/170 · 17
11
string ID 30
type: table cell
English
Semantics, Pre/Post-conditions
30/300 · 30
11
string ID 34
type: table cell
English
Type
4/100 · 4
82
string ID 82
type: paragraph
English
}; ```
6/100 · 6
11
string ID 39
type: table cell
English
expression
10/100 · 10
11
string ID 50
type: table title
English
Valid expressions
17/170 · 17
11
string ID 36
type: table cell
English
Semantics, Pre/Post-conditions
30/300 · 30
11
string ID 30
type: table cell
English
Normally the parser returns after successfully parsing a structured element (header, chunk header, or chunk body) even if there are octets remaining in the input. This is necessary when attempting to parse the header first, or when the caller wants to inspect information which may be invalidated by subsequent parsing, such as a chunk extension. The `eager` option controls whether the parser keeps going after parsing structured element if there are octets remaining in the buffer and no error occurs. This option is automatically set or cleared during certain stream operations to improve performance with no change in functionality.
636/6360 · 636
11
string ID 36
type: paragraph
English
A type modeling [*SyncStream] meets the following requirements:
63/630 · 63
11
string ID 21
type: table code
English
#include <experimental/io_context>
namespace net = std::experimental::net;
net::io_context ioc;
95/950 · 95
11
string ID 49
type: list
English
* Keep it simple.
17/170 · 17