User avatar admin

String added in the repository
When this value is `true`, the stream will support (but not require) the [@https://tools.ietf.org/html/rfc7692 permessage-deflate extension]. Whether or not the stream actually requests or accepts the extension during a handshake depends on a separate configurable option.

When the value is `false` the extension is disabled. Streams will never request the extension in the client role or accept a request for the extension in the server role. An additional benefit of disabling the extension is that compilation will be faster, and the resulting program executable will contain less code.
When this value is `true`, the stream will support (but not require) the [@https://tools.ietf.org/html/rfc7692 permessage-deflate extension]. Whether or not the stream actually requests or accepts the extension during a handshake depends on a separate configurable option.

When the value is `false` the extension is disabled. Streams will never request the extension in the client role or accept a request for the extension in the server role. An additional benefit of disabling the extension is that compilation will be faster, and the resulting program executable will contain less code.
06/05/2026
User avatar admin

String added in the repository
`deflateSupported`
`deflateSupported`
06/05/2026
User avatar admin

String added in the repository
The type of the next layer. An object of this type will be constructed and maintained for the lifetime of the stream. All reads and writes will go through the next layer. This type must meet the requirements of either __SyncStream__, __AsyncStream__, or both, depending on the style of I/O that is to be performed.
The type of the next layer. An object of this type will be constructed and maintained for the lifetime of the stream. All reads and writes will go through the next layer. This type must meet the requirements of either __SyncStream__, __AsyncStream__, or both, depending on the style of I/O that is to be performed.
06/05/2026
User avatar admin

String added in the repository
`NextLayer`
`NextLayer`
06/05/2026
User avatar admin

String added in the repository
Description
Description
06/05/2026
User avatar admin

String added in the repository
Name
Name
06/05/2026
User avatar admin

String added in the repository
WebSocket Stream Template Parameters
WebSocket Stream Template Parameters
06/05/2026
User avatar admin

String added in the repository
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:
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:
06/05/2026
User avatar admin

String added in the repository
Construction
Construction
06/05/2026
User avatar admin

String added in the repository
This documentation assumes familiarity with __Asio__ and
This documentation assumes familiarity with __Asio__ and
06/05/2026
User avatar admin

String added in the repository
Beast provides developers with a robust WebSocket implementation built on Boost.Asio with a consistent asynchronous model using a modern C++ approach.
Beast provides developers with a robust WebSocket implementation built on Boost.Asio with a consistent asynchronous model using a modern C++ approach.
06/05/2026
User avatar admin

String added in the repository
The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications needing two-way communication with servers without relying on opening multiple HTTP connections.
The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications needing two-way communication with servers without relying on opening multiple HTTP connections.
06/05/2026
User avatar admin

String added in the repository
WebSocket
WebSocket
06/05/2026
User avatar admin

Component created
Component created (boost_endpoint) 06/05/2026
User avatar None

Add-on installed
weblate.cleanup.generic 06/05/2026
User avatar None

Add-on installed
weblate.flags.same_edit 06/05/2026
User avatar admin

Changes committed
Changes committed 06/05/2026
User avatar admin

Resource updated
Parsing of the “doc/qbk/06_websocket/03_decorator.qbk” file was enforced. 06/05/2026
User avatar None

Alert triggered
No file mask matches. 06/05/2026
User avatar admin

Resource updated
File “doc/qbk/06_websocket/03_decorator.qbk” was added. 06/05/2026

Search