Exit Zen
14
string ID 25
type: table cell
English
[path_link example/http/client/async-ssl-system-executor/http_client_async_ssl_system_executor.cpp http_client_async_ssl_system_executor.cpp]
141/1410 · 141
14
string ID 21
type: table cell
English
__AsyncWriteStream__
20/200 · 20
14
string ID 40
type: paragraph
English
All synchronous stream operations come in two varieties. One which throws an exception upon error, and another which accepts as the last parameter an argument of type [link beast.ref.boost__beast__error_code `error_code&`]. If an error occurs this argument will be set to contain the error code.
295/2950 · 295
14
string ID 96
type: paragraph
English
Messages may optionally carry a body. The size of the message body is determined by the semantics of the message and the special fields Content-Length and Transfer-Encoding. [@https://tools.ietf.org/html/rfc7230#section-3.3 rfc7230 section 3.3] provides a comprehensive description for how the body length is determined.
320/3200 · 320
14
string ID 148
type: paragraph
English
Synchronous input and output is accomplished through blocking function calls that return with the result of the operation. Such operations typically cannot be canceled and do not have a method for setting a timeout. The __SyncReadStream__ and __SyncWriteStream__ concepts define requirements for ['synchronous streams]: a portable I/O abstraction that transfers data using buffer sequences to represent bytes and either `error_code` or an exception to report any failures. [@boost:/doc/html/boost_asio/reference/basic_stream_socket.html ['net::basic_stream_socket]] is a synchronous stream commonly used to form TCP/IP connections. User-defined types which meet the requirements are possible:
692/6920 · 692
14
string ID 80
type: table cell
English
__message__
11/110 · 11
14
string ID 66
type: table title
English
Header
6/100 · 6
14
string ID 29
type: table code
English
/// An HTTP/1 parser for producing a request message.
template<class Body, class Allocator = std::allocator<char>>
using request_parser = parser<true, Body, Allocator>;
168/1680 · 168
14
string ID 76
type: list
English
* [issue 3009] Removed moved sections from documentation
* [issue 3009] Removed superfluous log messages from tests
115/1150 · 115
14
string ID 51
type: table cell
English
Semantics, Pre/Post-conditions
30/300 · 30
14
string ID 30
type: table cell
English
`B::reader`
11/110 · 11
14
string ID 34
type: table cell
English
Return Type
11/110 · 11
14
string ID 93
type: list
English
* No stateful allocator support.
32/320 · 32
39
string ID 39
type: table cell
English
`W::const_buffers_type`
0/230 · 23
14
string ID 50
type: table cell
English
Semantics, Pre/Post-conditions
30/300 · 30
14
string ID 36
type: table cell
English
A type which meets the requirements of __FieldsWriter__.
56/560 · 56
14
string ID 30
type: table cell
English
[link beast.ref.boost__beast__http__basic_parser.body_limit `body_limit`]
73/730 · 73
14
string ID 63
type: paragraph
English
Boost.Beast depends specifically on the Boost.Asio flavor of Networking, although this may change in the future. While this library offers performant implementations of the HTTP and WebSocket network protocols, it depends on the networking interfaces to perform general tasks such as performing domain name resolution (DNS lookup), establishing outgoing connections, and accepting incoming connections. Callers are responsible for interacting with networking to initialize objects to the correct state where they are usable by this library.
540/5400 · 540
14
string ID 55
type: paragraph
English
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).
193/1930 · 193
14
string ID 45
type: table cell
English
Send a buffer sequence as part of a message.
44/440 · 44