User avatar Bstran

Translation changed
/// An HTTP response template<bool isRequest, class Fields, class Body> struct message<false, Fields, Body> {
/// An一个 HTTP response template响应模板<bool isRequest, class Fields, class Body> struct message<false, Fields, Body> {
06/20/2026
User avatar Bstran

Translation changed
};
};
126
06/20/2026
User avatar Bstran

Translation changed
/// An HTTP request template<class Fields, class Body> struct message<true, Fields, Body> {
/// An一个 HTTP request template请求模板<class Fields, class Body> struct message<true, Fields, Body> {
06/20/2026
User avatar Bstran

Translation changed
However, a problem arises. How do we write a function which can accept an object that is either a request or a response? As written, the only obvious solution is to make the message a template type. Additional traits classes would then be needed to make sure that the passed object has a valid type which meets the requirements. These unnecessary complexities are bypassed by making each container a partial specialization: ``` /// An HTTP message template<bool isRequest, class Fields, class Body> struct message;
However, a problem arises. How do we write a function which can accept an object that is either a request or a response? As written, the only obvious solution is to make the message a template type. Additional traits classes would then be needed to make sure that the passed object has a valid type which meets the requirements. These unnecessary complexities are bypassed by making each container a 然而，问题随之而来。如何编写一个既能接受请求对象又能接受响应对象的函数呢？按照当前的写法，最显而易见的解决方案是将消息类型设为模板参数。这样一来，还需要额外的特征类（traits classes）来确保传入的对象具有符合要求的有效类型。为了避免这些不必要的复杂性，我们可以将每个容器设计为偏特化（partial specialization: ）：``` /// An HTTP message template<bool isRequest, class Fields, class Body> struct message;
06/20/2026
User avatar Bstran

Translation changed
These containers are capable of representing everything in the model of HTTP requests and responses described in __rfc7230__. Request and response objects are different types. The user can choose the container used to represent the fields. And the user can choose the [*Body] type, which is a concept defining not only the type of `body` member but also the algorithms used to transfer information in and out of that member when performing serialization and parsing.
These containers are capable of representing everything in the model of HTTP requests and responses described in __rfc7230__. Request and response objects are different types. The user can choose the container used to represent the fields. And the user can choose the [*Body] type, which is a concept defining not only the type of `body` member but also the algorithms used to transfer information in and out of that member when performing serialization and parsing.这些容器能够完整地表达 RFC 7230 中描述的 HTTP 请求和响应模型。请求对象和响应对象是两种不同的类型。用户可以选择用于表示首部字段的容器。此外，用户还可以选择 `Body` 类型，该类型不仅定义了 `body` 成员的类型，还规定了在序列化和解析过程中，信息进出该成员所使用的算法。
06/20/2026
User avatar Bstran

Translation changed
Here is our first attempt at declaring some message containers:
Here is our first attempt at declaring some message containers:这是我们首次尝试声明一些消息容器：
06/20/2026
User avatar Bstran

Translation changed
We would also like our message container to have customization points permitting the following: allocator awareness, user-defined containers to represent header fields, and user-defined types and algorithms to represent the body. And finally, because requests and responses have different fields in the ['start-line], we would like the containers for requests and responses to be represented by different types for function overloading.
We would also like our message container to have customization points permitting the following: allocator awareness, user-defined containers to represent header fields, and user-defined types and algorithms to represent the body. And finally, because requests and responses have different fields in the ['start-line], we would like the containers for requests and responses to be represented by different types for function overloading.此外，我们还希望消息容器提供自定义扩展点，以实现以下功能：支持分配器感知（allocator awareness）、允许使用用户自定义的容器来表示首部字段，以及支持使用用户自定义的类型和算法来表示消息体。最后，由于请求和响应的起始行（start-line）包含不同的字段，我们希望分别使用不同的类型来表示请求和响应的容器，从而支持函数重载。
06/20/2026
User avatar Bstran

Translation changed
* `P(S(m)) == m`
* `P(S(m)) == m`
06/20/2026
User avatar Bstran

Translation changed
* `S(m) == x`
* `S(m) == x`
06/20/2026
User avatar Bstran

Translation changed
These relations are true:
These relations are true:以下关系成立：
06/20/2026
User avatar Bstran

Translation changed
* `P(x)` is a parsing function which produces a message container from
* `P(x)` is a parsing function which produces a message container from是一个解析函数，用于从……生成一个消息容器
06/20/2026
User avatar Bstran

Translation changed
* `S(m)` is a serialization function which produces a series of octets
* `S(m)` is a serialization function which produces a series of 是一个序列化函数，用于生成一系列字节（octets）
06/20/2026
User avatar Bstran

Translation changed
* `x` is a series of octets describing a valid HTTP message in
* `x` is a series of octets describing a valid HTTP message in是一系列字节（octets），用于描述一个有效的 HTTP 消息
06/20/2026
User avatar Bstran

Translation changed
* `m` is an instance of an HTTP message container
* `m` is an instance of an HTTP message container是 HTTP 消息容器的一个实例
06/20/2026
User avatar Bstran

Translation changed
In this section we describe the problem of modeling HTTP messages and explain how the library arrived at its solution, with a discussion of the benefits and drawbacks of the design choices. The goal for creating a message model is to create a container with value semantics, possibly movable and/or copyable, that contains all the information needed to serialize, or all of the information captured during parsing. More formally, given:
In this section we describe the problem of modeling HTTP messages and explain how the library arrived at its solution, with a discussion of the benefits and drawbacks of the design choices. The goal for creating a message model is to create a container with value semantics, possibly movable and/or copyable, that contains all the information needed to serialize, or all of the information captured during parsing. More formally, given:在本节中，我们将探讨 HTTP 消息建模所面临的挑战，并阐述该库是如何推导出最终解决方案的，同时也会深入剖析这些设计选择的利弊。构建消息模型的核心目标，是打造一个具备值语义（value semantics）的容器（支持移动和/或复制），使其能够囊括序列化所需的全部信息，或是完整保留解析过程中捕获的所有数据。从更严谨的层面来说，给定：
06/20/2026
User avatar Bstran

Translation changed
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2017. The presentation provides a simplified explanation of the design process for the HTTP message container used in Beast. The slides and code used are available in the [@https://github.com/vinniefalco/CppCon2017 GitHub repository].
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2017. The presentation provides a simplified explanation of the design process for the HTTP message container used in Beast. The slides and code used are available in the以下视频演示是在 2017 年的 [@https://cppcon.org/ CppCon] 上发表的。该演示简要介绍了 Beast 中使用的 HTTP 消息容器的设计过程。演示所用的幻灯片和代码可在 [@https://github.com/vinniefalco/CppCon2017 GitHub repository].仓库] 中找到。
06/20/2026
User avatar Bstran

Translation changed
HTTP Message Container __video__
HTTP Message Container消息容器 __video__
06/20/2026
User avatar Bstran

Contributor joined
Contributor joined 06/20/2026
User avatar None

Alert triggered
Repository has changes. 06/12/2026
User avatar None

Alert triggered
Repository has changes. 06/11/2026

Search