User avatar Bstran

Translation changed
A type modeling [*Stream] meets either or both of the following requirements:
A type modeling [*Stream] meets either or both of the following requirements:建模 [*Stream] 的类型满足以下一个或两个要求：
06/19/2026
User avatar Bstran

Translation changed
Stream
Stream流
06/19/2026
User avatar Bstran

Translation changed
Stream concepts are based on named requirements in networking:
流的概念是基于网络编程中的命名要求的：
06/19/2026
User avatar Bstran

Translation changed
Stream concepts are based on named requirements in networking:
Stream concepts are based on named requirements in networking:流的概念基于网络编程中的命名要求：
06/19/2026
User avatar Bstran

Translation changed
A stream in the context of Beast and networking, represents a full-duplex connection between two programs or hosts, where data represented as bytes may be received reliably in the same order they were written. Streams may support any combination of synchronous and/or asynchronous reading and writing.
A stream in the context of Beast and networking, represents a full-duplex connection between two programs or hosts, where data represented as bytes may be received reliably in the same order they were written. Streams may support any combination of synchronous and/or asynchronous reading and writing.在 Beast 和网络编程中，流用于表示两个程序或主机之间的全双工连接。数据以字节形式呈现，能够按写入顺序被可靠地接收。流支持同步与异步读写操作的任意组合。
06/19/2026
User avatar Bstran

Translation changed
Streams
Streams流
06/19/2026
User avatar Bstran

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

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

Translation changed
* [link beast.ref.boost__beast__simple_rate_policy `simple_rate_policy`]
* [link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`]
* [link beast.ref.boost__beast__simple_rate_policy `simple_rate_policy`]
* [link beast.ref.boost__beast__unlimited_rate_policy `unlimited_rate_policy`]
06/19/2026
User avatar Bstran

Translation changed
Models
Models模型
06/19/2026
User avatar Bstran

Translation changed
Exemplar
Exemplar示例
06/19/2026
User avatar Bstran

Translation changed
The implementation calls this function every time the internal timer expires. The policy object may optionally use this opportunity to calculate elapsed time and throughput, and/or inform the algorithm used to determine subsequently queried transfer limits.
The implementation calls this function every time the internal timer expires. The policy object may optionally use this opportunity to calculate elapsed time and throughput, and/or inform the algorithm used to determine subsequently queried transfer limits.每当内部计时器到期时，实现都会调用此函数。策略对象可以选择性地利用此机会来计算已用时间和吞吐量，和/或用于优化后续查询传输上限时所使用的算法。
06/19/2026
User avatar Bstran

Translation changed
`a.on_timer()`
`a.on_timer()`
06/19/2026
User avatar Bstran

Translation changed
The implementation calls this function to inform the policy that `n` bytes were successfully transferred in the most recent write operation. The policy object may optionally use this information to calculate throughputs and/or inform the algorithm used to determine subsequently queried transfer limits.
The implementation calls this function to inform the policy that `n` bytes were successfully transferred in the most recent write operation. The policy object may optionally use this information to calculate throughputs and/or inform the algorithm used to determine subsequently queried transfer limits.实现会调用此函数，以通知策略在最近一次写入操作中已成功传输了 `n` 个字节。策略对象可以选择性地利用此信息来计算吞吐量，和/或用于优化后续查询传输上限时所使用的算法。
06/19/2026
User avatar Bstran

Translation changed
`a.transfer_write_bytes(n)`
`a.transfer_write_bytes(n)`
06/19/2026
User avatar Bstran

Translation changed
The implementation calls this function to inform the policy that `n` bytes were successfully transferred in the most recent read operation. The policy object may optionally use this information to calculate throughputs and/or inform the algorithm used to determine subsequently queried transfer maximums.
The implementation calls this function to inform the policy that `n` bytes were successfully transferred in the most recent read operation. The policy object may optionally use this information to calculate throughputs and/or inform the algorithm used to determine subsequently queried transfer maximums.实现会调用此函数，以通知策略在最近一次读取操作中已成功传输了 `n` 个字节。策略对象可以选择性地利用此信息来计算吞吐量，和/或用于优化后续查询传输最大值时所使用的算法。
06/19/2026
User avatar Bstran

Translation changed
`a.transfer_read_bytes(n)`
`a.transfer_read_bytes(n)`
06/19/2026
User avatar Bstran

Translation changed
This function is called by the implementation to determine the maximum number of allowed bytes to be transferred in the next write operation. The actual number of bytes subsequently transferred may be less than this number.

If the policy returns a value of zero, the read operation will asynchronously wait until the next timer interval before retrying. When the retry occurs, this function will be called again.
This function is called by the implementation to determine the maximum number of allowed bytes to be transferred in the next write operation. The actual number of bytes subsequently transferred may be less than this number.

If the policy returns a value of zero, the read operation will asynchronously wait until the next timer interval before retrying. When the retry occurs, this function will be called again.实现会调用此函数，以确定下一次写入操作允许传输的最大字节数。随后实际传输的字节数可能会小于该数值。
如果该策略返回零值，写入操作将异步等待直到下一个计时器间隔再进行重试。当重试发生时，此函数将再次被调用。
06/19/2026
User avatar Bstran

Translation changed
`a.available_write_bytes()`
`a.available_write_bytes()`
06/19/2026
User avatar Bstran

Translation changed
This function is called by the implementation to determine the maximum number of allowed bytes to be transferred in the next read operation. The actual number of bytes subsequently transferred may be less than this number.

If the policy returns a value of zero, the read operation will asynchronously wait until the next timer interval before retrying. When the retry occurs, this function will be called again.
This function is called by the implementation to determine the maximum number of allowed bytes to be transferred in the next read operation. The actual number of bytes subsequently transferred may be less than this number.

If the policy returns a value of zero, the read operation will asynchronously wait until the next timer interval before retrying. When the retry occurs, this function will be called again.实现会调用此函数，以确定下一次读取操作允许传输的最大字节数。随后实际传输的字节数可能会小于该数值。

如果该策略返回零值，读取操作将异步等待直到下一个计时器间隔再进行重试。当重试发生时，此函数将再次被调用。
06/19/2026

Search