User avatar Bstran

Translation changed
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由于读取数据的调用可能返回数量不等的字节，因此读取数据的调用接口需要一个满足 __DynamicBuffer__ 要求的对象。该概念基于 __streambuf__. 建模。
06/18/2026
User avatar Bstran

Translation changed
Notes
Notes记录
06/18/2026
User avatar Bstran

Contributor joined
Contributor joined 06/18/2026
User avatar Bstran

Translation completed
Translation completed 06/18/2026
User avatar Bstran

Translation changed
To invoke the customization point, first bring the default implementation into scope with a `using` statement. Then call the customization point without namespace qualification, allowing argument-dependent lookup to take effect:
To invoke the customization point, first bring the default implementation into scope with a `using` statement. Then call the customization point without namespace qualification, allowing argument-dependent lookup to take effect:要调用该定制点，首先通过 `using` 声明将默认实现引入作用域，然后不使用命名空间限定符直接调用该定制点，以便让参数依赖查找（ADL）生效：
06/18/2026
User avatar Bstran

Translation changed
Invoking Teardown
调用拆除操作
06/18/2026
User avatar Bstran

Translation changed
Invoking Teardown
Invoking Teardown调用拆除
06/18/2026
User avatar Bstran

Translation changed
When the implementation invokes the asynchronous teardown function, it always uses an invokable completion handler. It is not necessary to specify the return type customization when creating user-defined overloads of `async_teardown`.
When the implementation invokes the asynchronous teardown function, it always uses an invokable completion handler. It is not necessary to specify the return type customization when creating user-defined overloads of `async_teardown`.当实现调用异步拆除函数时，总是传入一个可调用的完成处理器。定义 `async_teardown` 的自定义重载时，无需指定返回类型的定制。
06/18/2026
User avatar Bstran

Translation changed
To provide overloads of teardown for a user-defined type, simply declare the two free functions with the correct signature, accepting a reference to the user-defined type as the stream parameter:
To provide overloads of teardown for a user-defined type, simply declare the two free functions with the correct signature, accepting a reference to the user-defined type as the stream parameter:要为自定义类型提供拆除操作的重载，只需声明两个具有正确签名的自由函数，这些函数接受对自定义类型的引用作为流参数：
06/18/2026
User avatar Bstran

Translation changed
User-defined Teardown
User-defined Teardown用户自定义拆除
06/18/2026
User avatar Bstran

Translation changed
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.
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 webs当使用 Asio 类型 socket 或 ssl_stream 作为下一层来实例化 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.流时，实现会提供适当的拆除定制点重载，此时无需用户额外操作。但如果为自定义类型实例化 WebSocket 流，且未为该类型提供这些定制点，则会导致编译错误。另外，如果自定义类型封装了上述某个 Asio 对象，则可能需要调用被封装对象的拆除定制点。以下示例展示了如何完成这些操作。
06/18/2026
User avatar Bstran

Translation changed
* [link beast.ref.boost__beast__websocket__async_teardown `async_teardown`]:
* [link beast.ref.boost__beast__websocket__async_teardown `async_teardown`]:
06/18/2026
User avatar Bstran

Translation changed
* [link beast.ref.boost__beast__websocket__teardown `teardown`]: Overloads
* [link beast.ref.boost__beast__websocket__teardown `teardown`]: Overloads
06/18/2026
User avatar Bstran

Translation changed
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:
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:为使实现能够执行关闭操作中的关闭步骤，该库公开了两个定制点，它们是与下一层类型关联的自由函数：
06/18/2026
User avatar Bstran

Translation changed
The WebSocket protocol requirements described in rfc6455 section 7.1.1 outline an operation described as [@https://tools.ietf.org/html/rfc6455#section-7.1.1 ['Close the WebSocket Connection]]. This operation cleanly discards bytes remaining at receiving endpoints and also closes the underlying TCP/IP connection. Orderly shutdowns are always preferred; for TLS or SSL streams, a protocol-level shutdown is desired. This presents a small issue for the [link beast.ref.boost__beast__websocket__stream `stream`] implementation: the stream's `NextLayer` template type requires only __SyncStream__ or __AsyncStream__, but those concepts do not support the operations to shut down the connection.
The WebSocket protocol requirements described in rfc6455 section 7.1.1 outline an operation described as [@https://tools.ietf.org/html/rfc6455#section-7.1.1 ['Close the WebSocket Connection]]. This operation cleanly discards bytes remaining at receiving endpoints and also closes the underlying TCP/IP connection. Orderly shutdowns are always preferred; for协议规范（rfc6455 第 7.1.1 节）概述了一个称为“关闭 WebSocket 连接”的操作。该操作会清理接收端剩余字节，并同时关闭底层的 TCP/IP 连接。通常优先采用有序关闭方式；对于 TLS or或 SSL streams, a protocol-level shutdown is desired. This presents a small issue for the流，则需要进行协议级的关闭。这给 [link beast.ref.boost__beast__websocket__stream `stream`] implementation: the stream's `NextLayer` template type requires only __的实现带来一个小问题：流的 NextLayer 模板类型仅要求满足 SyncStream__ or __ 或 AsyncStream__, but those concepts do not support the operations to shut down the connection.，但这些概念并不支持关闭连接的操作。
06/18/2026
User avatar Bstran

Translation changed
Teardown
Teardown连接拆除
06/18/2026
User avatar Bstran

Contributor joined
Contributor joined 06/18/2026
User avatar Bstran

Translation completed
Translation completed 06/18/2026
User avatar Bstran

Translation changed
The timeouts on the websocket stream are incompatible with the timeouts used in the `tcp_stream`. When constructing a websocket stream from a tcp stream that has timeouts enabled, the timeout should be disabled first before constructing the websocket stream, as shown.
The timeouts on the websWebSocket stream are incompatible with the timeouts used in the `tcp_stream`. When constructing a webs流的超时机制与 tcp_stream 的超时机制不兼容。当从已启用超时的 tcp 流构造 WebSocket stream from a tcp stream that has timeouts enabled, the timeout should be disabled first before constructing the websocket stream, as shown.流时，应首先禁用 tcp 流的超时，如下所示。
06/18/2026
User avatar Bstran

Translation changed
Websocket timeout features are available only when using asynchronous I/O.
WebsSocket timeout features are available only when using asynchronous I/O.超时功能仅在异步 I/O 模式下可用。
06/18/2026

Search