Exit Zen
12
string ID 30
type: table cell
English
[link beast.ref.boost__beast__http__basic_parser.skip.overload2 `skip`]
71/710 · 71
12
string ID 38
type: list
English
* __SyncReadStream__
* __SyncWriteStream__
42/420 · 42
12
string ID 53
type: paragraph
English
This document refers to the three implementations above interchangeably and collectively as [*Networking] (or just ['networking]). The Boost.Asio and Asio flavors of Networking provide additional features not currently proposed for C++, but likely to appear in a future specification, such as:
293/2930 · 293
12
string ID 51
type: list
English
* Stay low level; don't invent a whole web server or client.
60/600 · 60
12
string ID 45
type: table cell
English
Send a buffer sequence as a complete message.
45/450 · 45
12
string ID 22
type: table cell
English
[link beast.ref.boost__beast__websocket__stream.set_option `stream::set_option`]
80/800 · 80
12
string ID 21
type: table cell
English
[link beast.ref.boost__beast__buffers_front `buffers_front`]
60/600 · 60
12
string ID 76
type: paragraph
English
For servers accepting incoming connections, the [link beast.ref.boost__beast__websocket__stream `websocket::stream`] can read the incoming upgrade request and automatically reply. If the handshake meets the requirements, the stream sends back the upgrade response with a [@https://tools.ietf.org/html/rfc6455#section-4.2.2 ['101 Switching Protocols]] status code. If the handshake does not meet the requirements, or falls outside the range of allowed parameters specified by stream options set previously by the caller, the stream sends back an HTTP response with a status code indicating an error. Depending on the keep alive setting, the connection may remain open for a subsequent handshake attempt. A typical HTTP Upgrade response created and sent by the implementation upon receiving an upgrade request handshake will look like this:
838/8380 · 838
12
string ID 36
type: table cell
English
Semantics, Pre/Post-conditions
30/300 · 30
12
string ID 17
type: table cell
English
[link beast.ref.boost__beast__file_posix `file_posix`]
54/540 · 54
12
string ID 38
type: table cell
English
`writer`
8/100 · 8
12
string ID 16
type: variablelist cell
English
The energy invested in Beast went into the design of the interfaces, not performance. That said, the most sensitive parts of Beast have been optimized or designed with optimization in mind. The slow parts of WebSocket processing have been optimized, and the HTTP parser design is lifted from another extremely popular project which has performance as a design goal (see [@https://github.com/h2o/picohttpparser]).

From: [@http://www.boost.org/development/requirements.html]

"Aim first for clarity and correctness; optimization should be only a secondary concern in most Boost libraries."

As the library matures it will undergo optimization passes; benchmarks will logically accompany this process. There is a small benchmarking program included in the tests which compares the performance of Beast's parser to the NodeJS reference parser, as well as some benchmarks which compare the performance of various Beast dynamic buffer implementations against Asio's.
961/9610 · 961
12
string ID 25
type: table cell
English
[link beast.ref.boost__beast__http__request_serializer `request_serializer`]
76/760 · 76
12
string ID 49
type: table title
English
Valid expressions
17/170 · 17
12
string ID 42
type: paragraph
English
There are three timeout settings which may be set independently on the stream:
78/780 · 78
12
string ID 54
type: list
English
* [link beast.ref.boost__beast__websocket__stream.async_read `async_read`] or [link beast.ref.boost__beast__websocket__stream.async_read_some `async_read_some`]
* [link beast.ref.boost__beast__websocket__stream.async_write `async_write`] or [link beast.ref.boost__beast__websocket__stream.async_write_some `async_write_some`]
* [link beast.ref.boost__beast__websocket__stream.async_ping `async_ping`] or [link beast.ref.boost__beast__websocket__stream.async_pong `async_pong`]
* [link beast.ref.boost__beast__websocket__stream.async_close `async_close`]
553/5530 · 553
12
string ID 78
type: paragraph
English
The `tcp_stream` is designed as a replacement for [@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html `net::ip::tcp::socket`]. Any program which currently uses a socket, can switch to a `tcp_stream` and achieve the features above (although some interfaces are different, see below). Networking now allows I/O objects to construct with any instance of __ExecutionContext__ or __Executor__ objects. Here we construct a stream which uses a particular I/O context to dispatch completion handlers:
499/4990 · 499
12
string ID 63
type: paragraph
English
Here is our first attempt at declaring some message containers:
63/630 · 63
12
string ID 50
type: table cell
English
`deflateSupported`
18/180 · 18
12
string ID 83
type: paragraph
English
The WebSocket protocol defines a procedure and control message for initiating a close of the session. In this procedure, a host requests the close by sending a [@https://tools.ietf.org/html/rfc6455#section-5.5.1 ['close frame]]. To request a close use a close function such as [link beast.ref.boost__beast__websocket__stream.close.overload2 `close`] or [link beast.ref.boost__beast__websocket__stream.async_close `async_close`]:
428/4280 · 428