Exit Zen
6
string ID 32
type: heading
English
Requirements
12/120 · 12
6
string ID 25
type: paragraph
English
In this table:
14/140 · 14
6
string ID 24
type: list
English
* [*AsyncStream]
* [*SyncStream]
32/320 · 32
6
string ID 21
type: table cell
English
__Asio__
8/100 · 8
6
string ID 24
type: list
English
* Role-symmetric interfaces; client and server the same (or close to it).
73/730 · 73
6
string ID 41
type: heading
English
Sending
7/100 · 7
6
string ID 22
type: table cell
English
[link beast.ref.boost__beast__websocket__request_type `request_type`]
69/690 · 69
6
string ID 27
type: heading
English
Requirements
12/120 · 12
6
string ID 34
type: paragraph
English
The implementation provides suitable overloads of the teardown customization points when websocket streams are instantiated using the Asio types __socket__ or __ssl_stream__ for the next layer. In this case no user action is required. However, when the websocket stream is instantiated for a user-defined type, compile errors will result if the customization points are not provided for the user defined type. Furthermore, user-defined types that wrap one of the Asio objects mentioned earlier may wish to invoke a teardown customization point for the wrapped object. This is how those tasks are accomplished.
609/6090 · 609
6
string ID 30
type: heading
English
Associated Types
16/160 · 16
6
string ID 16
type: variablelist cell
English
"I just want to download a resource using HTTP" is a common cry from users and reviewers. Such functionality is beyond the scope of Beast. Building a full featured HTTP client is a difficult task and large enough to deserve its own library. There are many things to deal with such as the various message body encodings, complex parsing of headers, difficult header semantics such as Range and Cache-Control, redirection, Expect:100-continue, connection retrying, domain name resolution, TLS, and much, much more. It is the author's position that Boost first needs a common set of nouns and verbs for manipulating HTTP at the protocol level; Beast provides that language.
670/6700 · 670
6
string ID 21
type: paragraph
English
These tasks may be performed by using the serializer stream interfaces. To use these interfaces, first construct an appropriate serializer from the message to be sent:
167/1670 · 167
6
string ID 27
type: list
English
* [link beast.ref.boost__beast__http__is_body_reader `is_body_reader`]
* __Body__
81/810 · 81
6
string ID 22
type: table cell
English
[link beast.ref.boost__beast__websocket__stream_base__timeout `stream_base::timeout`]
85/850 · 85
6
string ID 28
type: paragraph
English
Calls to asynchronous initiation functions support the extensible asynchronous model developed by the Boost.Asio author, allowing for traditional completion handlers, stackful or stackless coroutines, and even futures:
218/2180 · 218
6
string ID 50
type: paragraph
English
To simplify the handling of timeouts, these provided types wrap a [@boost:/doc/html/boost_asio/reference/basic_stream_socket.html `net::basic_stream_socket`] to provide additional features:
189/1890 · 189
6
string ID 43
type: list
English
* `S(m)` is a serialization function which produces a series of octets
70/700 · 70
6
string ID 41
type: paragraph
English
A WebSocket connection requires a stateful object, represented in Beast by a single class template [link beast.ref.boost__beast__websocket__stream `websocket::stream`]. The interface uses the layered stream model. A websocket stream object contains another stream object, called the "next layer", which it uses to perform I/O. Descriptions of each template parameter follow:
374/3740 · 374
6
string ID 31
type: section title
English
Simple WebSocket Client __example__
35/350 · 35
6
string ID 44
type: heading
English
Control Callback
16/160 · 16