User avatar Bstran

Translation changed
[*0]
[*0]
06/15/2026
User avatar Bstran

Translation changed
For ultimate control, the use of library stream algorithms may be bypassed entirely and instead work directly with buffers by calling members of __parser__ or __serializer__.
For ultimate control, the use of library stream algorithms may be bypassed entirely and instead work directly with buffers by calling members of若需最高级别的控制，可以完全绕过库的流算法，直接通过调用 __parser__ or或 __serializer__. 的成员函数来操作缓冲区。
06/15/2026
User avatar Bstran

Translation changed
buffers
buffers缓冲区
06/15/2026
User avatar Bstran

Translation changed
[*1]
[*1]
06/15/2026
User avatar Bstran

Translation changed
Until now parse and serialize operations apply or remove the chunked transfer coding as needed for message payloads whose size is not known ahead of time. For some domain specific niches, it is necessary to assume direct control over incoming or outgoing chunks in a chunk encoded message payload. For parsing this is achieved by setting hooks using the functions [link beast.ref.boost__beast__http__parser.on_chunk_header `on_chunk_header`] and/or [link beast.ref.boost__beast__http__parser.on_chunk_body `on_chunk_body`]. For serializing callers may first emit the header, and then use these buffer sequence adapters to control the contents of each chunk including [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk extensions]] and the [@https://tools.ietf.org/html/rfc7230#section-4.1.2 ['trailer-part]]: [link beast.ref.boost__beast__http__chunk_body `chunk_body`], [link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`], [link beast.ref.boost__beast__http__chunk_header `chunk_header`], and [link beast.ref.boost__beast__http__chunk_last `chunk_last`].
Until now parse and serialize operations apply or remove the chunked transfer coding as needed for message payloads whose size is not known ahead of time. For some domain specific niches, it is necessary to assume direct control over incoming or outgoing chunks in a chunk encoded message payload. For parsing this is achieved by setting hooks using the functions到目前为止，解析和序列化操作会根据需要自动对消息体应用或移除分块传输编码。但在某些特定领域，需要对分块编码的消息体中的传入或传出数据块进行直接控制。在解析端，可以通过设置钩子来实现：使用 [link beast.ref.boost__beast__http__parser.on_chunk_header `on_chunk_header`] and/or和/或 [link beast.ref.boost__beast__http__parser.on_chunk_body `on_chunk_body`]. For serializing callers may first emit the header, and then use these buffer sequence adapters to control the contents of each chunk including [@https://tools.ietf.org/html/rfc7230#section-4.1.1 ['chunk extensions]] and the [@https://tools.ietf.org/html/rfc7230#section-4.1.2 ['trailer-part]]: 函数。在序列化端，调用方可以先发送消息头部，然后使用以下缓冲区序列适配器来控制每个数据块的内容，包括分块扩展和尾部部分：[link beast.ref.boost__beast__http__chunk_body `chunk_body`], 、[link beast.ref.boost__beast__http__chunk_crlf `chunk_crlf`], 、[link beast.ref.boost__beast__http__chunk_header `chunk_header`], and 以及 [link beast.ref.boost__beast__http__chunk_last `chunk_last`].。
06/15/2026
User avatar weblate:commit

Changes committed
Changes committed 06/15/2026
User avatar Bstran

Translation changed
[@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked-body]]
[@https://tools.ietf.org/html/rfc7230#section-4.1 ['chunked-body]]
06/14/2026
User avatar Bstran

Translation changed
[*2]
[*2]
06/14/2026
User avatar Bstran

Translation changed
All of the stream operations at higher levels thus far have operated on a complete header or message. At this level it is possible to send and receive messages incrementally. This allows resource constrained implementations to perform work bounded on storage, or allows better control when setting timeouts for example. These functions read or write bounded amounts of data and return the number of bytes transacted: [link beast.ref.boost__beast__http__read_some.overload2 `read_some`], [link beast.ref.boost__beast__http__write_some.overload2 `write_some`], [link beast.ref.boost__beast__http__async_read_some `async_read_some`], and [link beast.ref.boost__beast__http__async_write_some `async_write_some`].
All of the stream operations at higher levels thus far have operated on a complete header or message. At this level it is possible to send and receive messages incrementally. This allows resource constrained implementations to perform work bounded on storage, or allows better control when setting timeouts for example. These functions read or write bounded amounts of data and return the number of bytes transacted: 到目前为止，所有较高层次的流操作都针对完整的消息头部或完整消息进行。而在此层次，则可以实现消息的增量式发送与接收。这对资源受限的实现特别有用，可以在有限的存储空间内完成任务，或在设置超时等场景下提供更精细的控制。以下函数用于读取或写入限定量的数据，并返回实际传输的字节数：[link beast.ref.boost__beast__http__read_some.overload2 `read_some`], 、[link beast.ref.boost__beast__http__write_some.overload2 `write_some`], 、[link beast.ref.boost__beast__http__async_read_some `async_read_some`], and 以及 [link beast.ref.boost__beast__http__async_write_some `async_write_some`].。
06/14/2026
User avatar Bstran

Translation changed
partial __message__
partial __message部分 __消息__
06/13/2026
User avatar Bstran

Translation changed
[*3]
[*3]
06/13/2026
User avatar Bstran

Translation changed
Sometimes it is necessary to first send or receive the HTTP header. For example, to read the header and take action before continuing to read the body. These functions use a __parser__ or __serializer__ to read or write the header: [link beast.ref.boost__beast__http__read_header.overload2 `read_header`], [link beast.ref.boost__beast__http__write_header.overload2 `write_header`], [link beast.ref.boost__beast__http__async_read_header `async_read_header`], and [link beast.ref.boost__beast__http__async_write_header `async_write_header`].
Sometimes it is necessary to first send or receive the HTTP header. For example, to read the header and take action before continuing to read the body. These functions use a有时需要先发送或接收 HTTP 头部，例如在读取头部后根据其内容决定后续操作，然后再继续读取消息体。以下函数使用 __parser__ or或 __serializer__ to read or write the header: 来读取或写入头部：[link beast.ref.boost__beast__http__read_header.overload2 `read_header`], 、[link beast.ref.boost__beast__http__write_header.overload2 `write_header`], 、[link beast.ref.boost__beast__http__async_read_header `async_read_header`], and 以及 [link beast.ref.boost__beast__http__async_write_header `async_write_header`].。
06/13/2026
User avatar Bstran

Translation changed
__header__
__header头部__
06/13/2026
User avatar Bstran

Translation changed
[*4]
[*4]
06/13/2026
User avatar Bstran

Translation changed
For more control, callers may take responsibility for managing the required __parser__ or __serializer__ transient state objects. This allows additional configuration such as limiting the number of bytes for message components during parsing, or regulating the size of buffers emitted during output. These functions send or receive complete messages using a serializer or parser: [link beast.ref.boost__beast__http__read.overload2 `read`], [link beast.ref.boost__beast__http__write.overload2 `write`], [link beast.ref.boost__beast__http__async_read.overload1 `async_read`], and [link beast.ref.boost__beast__http__async_write.overload1 `async_write`].
For more control, callers may take responsibility for managing the required若需更多控制权，调用方可以自行管理所需的 __parser__ or或 __serializer__ transient state objects. This allows additional configuration such as limiting the number of bytes for message components during parsing, or regulating the size of buffers emitted during output. These functions send or receive complete messages using a serializer or parser: 临时状态对象。这样便可以实现额外配置，例如在解析过程中限制消息组件的最大字节数，或控制输出时缓冲区的大小。以下函数通过使用解析器或序列化器来发送或接收完整消息：[link beast.ref.boost__beast__http__read.overload2 `read`], 、[link beast.ref.boost__beast__http__write.overload2 `write`], 、[link beast.ref.boost__beast__http__async_read.overload1 `async_read`], and 以及 [link beast.ref.boost__beast__http__async_write.overload1 `async_write`].。
06/13/2026
User avatar Bstran

Translation changed
__parser__, __serializer__
__parser__, __serializer解析器__, __序列化器__
06/13/2026
User avatar Bstran

Translation changed
[*5]
[*5]
06/13/2026
User avatar Bstran

Translation changed
At the highest level, these free functions send or receive a complete HTTP message in one call. They are designed for ease of use: [link beast.ref.boost__beast__http__read.overload4 `read`], [link beast.ref.boost__beast__http__write.overload4 `write`], [link beast.ref.boost__beast__http__async_read.overload2 `async_read`], and [link beast.ref.boost__beast__http__async_write.overload2 `async_write`].
At the highest level, these free functions send or receive a complete HTTP message in one call. They are designed for ease of use: 最顶层接口通过一次函数调用即可完成完整 HTTP 消息的发送或接收，旨在简化使用。相关函数包括：[link beast.ref.boost__beast__http__read.overload4 `read`], 、[link beast.ref.boost__beast__http__write.overload4 `write`], 、[link beast.ref.boost__beast__http__async_read.overload2 `async_read`], and 以及 [link beast.ref.boost__beast__http__async_write.overload2 `async_write`].。
06/13/2026
User avatar Bstran

Translation changed
__message__
__message消息__
06/13/2026
User avatar Bstran

Translation changed
[*6]
[*6]
06/13/2026

Search