User avatar admin

Resource updated
File “doc/qbk/06_websocket/08_notes.qbk” was added. 06/05/2026
User avatar admin

String added in the repository
The implementation uses composed asynchronous operations; although some individual operations can perform both reads and writes, this behavior is coordinated internally to make sure the underlying stream is operated in a safe fashion. This allows an asynchronous read operation to respond to a received ping frame even while a user-initiated call to asynchronous write is active.
The implementation uses composed asynchronous operations; although some individual operations can perform both reads and writes, this behavior is coordinated internally to make sure the underlying stream is operated in a safe fashion. This allows an asynchronous read operation to respond to a received ping frame even while a user-initiated call to asynchronous write is active.
06/05/2026
User avatar admin

String added in the repository
However, this code is correct:
However, this code is correct:
06/05/2026
User avatar admin

String added in the repository
For example, the following code is produces undefined behavior, because the program is attempting to perform two simultaneous reads:
For example, the following code is produces undefined behavior, because the program is attempting to perform two simultaneous reads:
06/05/2026
User avatar admin

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

String added in the repository
Like a regular __Asio__ socket, a [link beast.ref.boost__beast__websocket__stream `stream`] is not thread safe. Callers are responsible for synchronizing operations on the socket using an implicit or explicit strand, as per the Asio documentation. The websocket stream asynchronous interface supports one of each of the following operations to be active at the same time:
Like a regular __Asio__ socket, a [link beast.ref.boost__beast__websocket__stream `stream`] is not thread safe. Callers are responsible for synchronizing operations on the socket using an implicit or explicit strand, as per the Asio documentation. The websocket stream asynchronous interface supports one of each of the following operations to be active at the same time:
06/05/2026
User avatar admin

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

String added in the repository
The creation and operation of the __io_context__ associated with the underlying stream is left to the callers, permitting any implementation strategy including one that does not require threads for environments where threads are unavailable. Beast WebSocket itself does not use or require threads.
The creation and operation of the __io_context__ associated with the underlying stream is left to the callers, permitting any implementation strategy including one that does not require threads for environments where threads are unavailable. Beast WebSocket itself does not use or require threads.
06/05/2026
User avatar admin

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

String added in the repository
The example programs that come with the library demonstrate the usage of websocket stream operations with all asynchronous varieties.
The example programs that come with the library demonstrate the usage of websocket stream operations with all asynchronous varieties.
06/05/2026
User avatar admin

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

String added in the repository
Asynchronous versions are available for all functions:
Asynchronous versions are available for all functions:
06/05/2026
User avatar admin

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

String added in the repository
The implementation does not perform queueing or buffering of messages. If desired, these features should be provided by callers. The impact of this design is that library users are in full control of the allocation strategy used to store data and the back-pressure applied on the read and write side of the underlying TCP/IP connection.
The implementation does not perform queueing or buffering of messages. If desired, these features should be provided by callers. The impact of this design is that library users are in full control of the allocation strategy used to store data and the back-pressure applied on the read and write side of the underlying TCP/IP connection.
06/05/2026
User avatar admin

String added in the repository
Because calls to read data may return a variable amount of bytes, the interface to calls that read data require an object that meets the requirements of __DynamicBuffer__. This concept is modeled on __streambuf__.
Because calls to read data may return a variable amount of bytes, the interface to calls that read data require an object that meets the requirements of __DynamicBuffer__. This concept is modeled on __streambuf__.
06/05/2026
User avatar admin

String added in the repository
Notes
Notes
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

Search