Exit Zen
3
string ID 16
type: paragraph
English
The general strategy used by the author to evaluate external libraries is as follows:
85/850 · 85
3
string ID 17
type: heading
English
Associated Types
16/160 · 16
3
string ID 20
type: list
English
* A body that does not entirely fit in memory.
* A body produced incrementally from coroutine output.
* A body represented by zero or more buffers already in memory.
* A body whose size is not known ahead of time.
* Body data generated dynamically from other threads.
* Body data computed algorithmically.
305/3050 · 305
3
string ID 18
type: heading
English
Associated Types
16/160 · 16
3
string ID 18
type: paragraph
English
Stream concepts are based on named requirements in networking:
62/620 · 62
3
string ID 21
type: table title
English
Networking Implementations
26/260 · 26
3
string ID 18
type: list
English
* Don't try to do too much.
27/270 · 27
3
string ID 23
type: paragraph
English
The boundaries between frames of a multi-frame message are not not considered part of the message. Intermediaries such as proxies which forward the websocket traffic are free to "reframe" (split frames and combine them) the message in arbitrary ways. These intermediaries include Beast, which can reframe messages automatically in some cases depending on the options set on the stream.
385/3850 · 385
3
string ID 14
type: list
English
* __ConstBufferSequence__
* __MutableBufferSequence__
53/530 · 53
21
string ID 21
type: table title
English
Buffer Algorithms and Types
27/270 · 27
3
string ID 16
type: paragraph
English
A WebSocket session begins when a client sends the HTTP/1.1 [@https://tools.ietf.org/html/rfc7230#section-6.7 Upgrade] request for [@https://tools.ietf.org/html/rfc6455#section-1.3 WebSocket] on an established connection, and the server sends an appropriate response indicating that the request was accepted and that the connection has been upgraded. The Upgrade request must include the [@https://tools.ietf.org/html/rfc7230#section-5.4 Host] field, and the [@https://tools.ietf.org/html/rfc7230#section-5.3 target] of the resource to request. A typical HTTP Upgrade request created and sent by the implementation will look like this:
635/6350 · 635
3
string ID 18
type: heading
English
Associated Types
16/160 · 16
3
string ID 17
type: table title
English
File Types
10/100 · 10
3
string ID 24
type: paragraph
English
To enable the implementation to perform the shutdown components of the close operation, the library exposes two customization points expressed as free functions associated with the next layer type:
197/1970 · 197
3
string ID 15
type: paragraph
English
The generator will be asked to produce buffers. The consuming code will signal how much of the data has been consumed, and repeatedly query for buffers until no more data is available, or the generator indicates an error condition.
231/2310 · 231
3
string ID 16
type: variablelist cell
English
"Beast does not offer an HTTP server?"
38/380 · 38
3
string ID 21
type: list
English
* Inspect incoming header fields and keep or discard them.
58/580 · 58
3
string ID 15
type: list
English
* Send the header first, and the body later.
44/440 · 44
3
string ID 19
type: list
English
* Storing a body in a dynamic buffer
* Storing a body in a user defined container with a custom allocator
* Transformation of incoming body data before storage, for example
172/1720 · 172
3
string ID 22
type: table title
English
WebSocket Timeout Interface
27/270 · 27