Zen

Translation

type: paragraph
This representation addresses a narrow range of use cases. It has limited potential for customization and performance. It is more difficult to use because it excludes the start line fields from the model.
73/2050 · 205

Sign in to save translations.

Key English Chinese (Simplified Han script) Actions
* The `string<Tag> customization point constrains user defined body types
* `string<Tag>` 自定义点限制了用户自定义主体类型
The design of the message container in this library is cumbersome with its system of customization using trait specializations. The use of these customizations is extremely limited due to the way they are used in the container declaration, making the design overly complex without corresponding benefit.
该库消息容器的设计非常繁琐，其自定义系统依赖于特征（trait）特化。由于这些自定义机制在容器声明中的使用方式极为受限，导致该设计过于复杂，却未能带来相应的收益。
Boost.HTTP
Boost.HTTP
is a library resulting from the 2014 Google Summer of Code. It was submitted for a Boost formal review and rejected in 2015. It is based on Boost.Asio, and development on the library has continued to the present. As of the branch previously linked, it uses these message declarations: ``` template<class Headers, class Body> struct basic_message {
是一个源自 2014 年 Google Summer of Code 的库。它曾于 2015 年提交进行 Boost 正式审查，但遭到拒绝。该库基于 Boost.Asio 构建，其开发工作一直持续至今。在之前链接的分支中，它使用了如下的消息声明：``` template struct basic_message {
166
private:
private:
170
};
};
typedef basic_message<boost::http::headers, std::vector<std::uint8_t>> message;
typedef basic_message<boost::http::headers, std::vector<std::uint8_t>> message;
template<class Headers, class Body> struct is_message<basic_message<Headers, Body>>: public std::true_type {}; ```
template<class Headers, class Body> struct is_message<basic_message<Headers, Body>>: public std::true_type {}; ```
* This container cannot model a complete message. The ['start-line] items
* 该容器无法对完整的消息进行建模。['start-line] 项
* `headers_`, `body_`, and `trailers_` may only be default-constructed,
* `headers_`、`body_` 和 `trailers_` 只能进行默认构造，
* There is no way to defer the commitment of the [*Body] type to after
* 无法将 [*Body] 类型的提交推迟到之后进行
* No stateful allocator support. This follows from the previous limitation
* 不支持有状态分配器。这是由前一个限制导致的
* The trailers are stored in a separate object. Aside from the combinatorial
* 尾部（trailers）存储在一个单独的对象中。除了组合爆炸的问题之外
* The declarations imply that `std::vector` is a model of [*Body].
* 这些声明暗示 `std::vector` 是 [*Body] 的一个模型。
* The [*Body] customization point constrains user defined types to
* [*Body] 自定义点将用户自定义类型限制为
This representation addresses a narrow range of use cases. It has limited potential for customization and performance. It is more difficult to use because it excludes the start line fields from the model.
* 这种表示法仅能解决一小部分用例。其自定义潜力和性能表现均十分有限。由于该模型将起始行（start line）字段排除在外，导致其使用难度增加。
C++ REST SDK (cpprestsdk)
C++ REST SDK (cpprestsdk)
is a Microsoft project which ['"...aims to help C++ developers connect to and interact with services"]. It offers the most functionality of the libraries reviewed here, including support for Websocket services using its websocket++ dependency. It can use native APIs such as HTTP.SYS when building Windows based applications, and it can use Boost.Asio. The WebSocket module uses Boost.Asio exclusively.
是一个微软项目，其目标是“帮助 C++ 开发者连接服务并与之交互”。在本文所评测的库中，它的功能最为全面，包括通过其 websocket++ 依赖项来支持 WebSocket 服务。在构建基于 Windows 的应用程序时，它能够使用诸如 HTTP.SYS 等原生 API，同时也支持使用 Boost.Asio。其中，WebSocket 模块专门且排他性地使用了 Boost.Asio。
As cpprestsdk is developed by a large corporation, it contains quite a bit of functionality and necessarily has more interfaces. We will break down the interfaces used to model messages into more manageable pieces. This is the container used to store the HTTP header fields: ``` class http_headers { public:
由于 cpprestsdk 由大型公司（微软）开发，它包含了相当多的功能，因此也必然拥有更多的接口。我们将把用于建模消息的接口拆解为更易于管理的部分。以下是用于存储 HTTP 头字段的容器： ``` class http_headers { public:
254
private:
private:
256
}; ```
}; ```
This declaration is quite bare-bones. We note the typical problems of most field containers:
这个声明相当简陋。我们注意到大多数字段容器都存在一些典型问题：
* The container may only be default-constructed.
* 该容器只能进行默认构造。
* No support for allocators, stateful or otherwise.
* 不支持分配器，无论是有状态分配器还是其他类型的分配器。
* There are no customization points at all.
* 完全没有任何自定义点。
Now we analyze the structure of the larger message container. The library uses a handle/body idiom. There are two public message container interfaces, one for requests (`http_request`) and one for responses (`http_response`). Each interface maintains a private shared pointer to an implementation class. Public member function calls are routed to the internal implementation. This is the first implementation class, which forms the base class for both the request and response implementations: ``` namespace details {
现在，我们来分析更大的消息容器的结构。该库使用了句柄/主体惯用法（handle/body idiom）。它提供了两个公开的消息容器接口，一个用于请求（`http_request`），另一个用于响应（`http_response`）。每个接口都维护着一个指向实现类的私有共享指针。公开的成员函数调用会被路由到内部的实现。以下是第一个实现类，它构成了请求和响应实现类的基类： ``` namespace details {
class http_msg_base { public:
class http_msg_base { public:
protected:
protected:
306
}; ```
}; ```
To understand these declarations we need to first understand that cpprestsdk uses the asynchronous model defined by Microsoft's [@https://msdn.microsoft.com/en-us/library/dd504870.aspx [*Concurrency Runtime]]. Identifiers from the [@https://msdn.microsoft.com/en-us/library/jj987780.aspx [*`pplx` namespace]] define common asynchronous patterns such as tasks and events. The `concurrency::streams::istream` parameter and `m_data_available` data member indicates a lack of separation of concerns. The representation of HTTP messages should not be conflated with the asynchronous model used to serialize or parse those messages in the message declarations.
要理解这些声明，需要先了解 cpprestsdk 使用了微软的 [@https://msdn.microsoft.com/en-us/library/dd504870.aspx [*Concurrency Runtime]] 所定义的异步模型。来自 [@https://msdn.microsoft.com/en-us/library/jj987780.aspx [*`pplx` namespace]] 的标识符定义了任务和事件等通用异步模式。`concurrency::streams::istream` 参数和 `m_data_available` 数据成员表明存在关注点分离缺失的问题。在消息声明中，不应将 HTTP 消息的表示形式与用于序列化或解析这些消息的异步模型混为一谈。
The next declaration forms the complete implementation class referenced by the handle in the public interface (which follows after): ``` /// Internal representation of an HTTP request message. class _http_request final : public http::details::http_msg_base, public std::enable_shared_from_this<_http_request> { public:
以下声明构成了公开接口中的句柄所引用的完整实现类（该类位于后续）：``` /// HTTP 请求消息的内部表示。 class _http_request final : public http::details::http_msg_base, public std::enable_shared_from_this<_http_request> { public:
Key English Chinese (Simplified Han script) Actions
This representation addresses a narrow range of use cases. It has limited potential for customization and performance. It is more difficult to use because it excludes the start line fields from the model.
* 这种表示法仅能解决一小部分用例。其自定义潜力和性能表现均十分有限。由于该模型将起始行（start line）字段排除在外，导致其使用难度增加。
typedef basic_message<boost::http::headers, std::vector<std::uint8_t>> message;
typedef basic_message<boost::http::headers, std::vector<std::uint8_t>> message;
template<class Headers, class Body> struct is_message<basic_message<Headers, Body>>: public std::true_type {}; ```
template<class Headers, class Body> struct is_message<basic_message<Headers, Body>>: public std::true_type {}; ```
* `headers_`, `body_`, and `trailers_` may only be default-constructed,
* `headers_`、`body_` 和 `trailers_` 只能进行默认构造，
* There is no way to defer the commitment of the [*Body] type to after
* 无法将 [*Body] 类型的提交推迟到之后进行
* No stateful allocator support. This follows from the previous limitation
* 不支持有状态分配器。这是由前一个限制导致的
* The trailers are stored in a separate object. Aside from the combinatorial
* 尾部（trailers）存储在一个单独的对象中。除了组合爆炸的问题之外
This declaration is quite bare-bones. We note the typical problems of most field containers:
这个声明相当简陋。我们注意到大多数字段容器都存在一些典型问题：
There are a few C++ published libraries which implement some of the HTTP protocol. We analyze the message model chosen by those libraries and discuss the advantages and disadvantages relative to Beast.
目前已有一些 C++ 库实现了部分 HTTP 协议。我们将分析这些库所采用的消息模型，并讨论它们相对于 Beast 的优缺点。
* Review the message model. Can it represent a complete request or
* 审查消息模型。它能否表示一个完整的请求或
* Review the stream abstraction. This is the type of object, such as
* 审查流抽象层。这是一种对象类型，例如
* Check treatment of buffers. Does the library manage the buffers
* 检查缓冲区处理方式。该库是否负责管理缓冲区
Declarations examples from external libraries have been edited:
来自外部库的声明示例已做编辑：
cpp-netlib
cpp-netlib
is a network programming library previously intended for Boost but not having gone through formal review. As of this writing it still uses the Boost name, namespace, and directory structure although the project states that Boost acceptance is no longer a goal. The library is based on Boost.Asio and bills itself as ['"a collection of network related routines/implementations geared towards providing a robust cross-platform networking library"]. It cites ['"Common Message Type"] as a feature. As of the branch previous linked, it uses these declarations: ``` template <class Tag> struct basic_message {
cpp-netlib 是一个网络编程库，原本计划纳入 Boost，但并未通过正式审查。在撰写本文时，它仍然使用 Boost 的名称、命名空间和目录结构，尽管该项目声明不再将纳入 Boost 作为目标。该库基于 Boost.Asio，自称是“一组与网络相关的例程/实现，旨在提供一个健壮的跨平台网络库”。它将“通用消息类型”列为其特性之一。在上述链接的分支中，它使用了以下声明：
``` template struct basic_message {
* The use of `string_type` (a customization point) for source,
* 对源（source）使用 `string_type`（一个自定义点），
is a library resulting from the 2014 Google Summer of Code. It was submitted for a Boost formal review and rejected in 2015. It is based on Boost.Asio, and development on the library has continued to the present. As of the branch previously linked, it uses these message declarations: ``` template<class Headers, class Body> struct basic_message {
是一个源自 2014 年 Google Summer of Code 的库。它曾于 2015 年提交进行 Boost 正式审查，但遭到拒绝。该库基于 Boost.Asio 构建，其开发工作一直持续至今。在之前链接的分支中，它使用了如下的消息声明：``` template struct basic_message {
166
private:
private:
170
};
};
254
private:
private:
256
}; ```
}; ```
306
}; ```
}; ```
336
private:
private:
344
};
};
407
private:
private:
412
}; ```
}; ```
82
}; ```
}; ```

Loading…

User avatar Bstran

Translation changed
This representation addresses a narrow range of use cases. It has limited potential for customization and performance. It is more difficult to use because it excludes the start line fields from the model.
This representation addresses a narrow range of use cases. It has limited potential for customization and performance. It is more difficult to use because it excludes the start line fields from the model.* 这种表示法仅能解决一小部分用例。其自定义潜力和性能表现均十分有限。由于该模型将起始行（start line）字段排除在外，导致其使用难度增加。
06/20/2026
User avatar admin

String added in the repository
This representation addresses a narrow range of use cases. It has limited potential for customization and performance. It is more difficult to use because it excludes the start line fields from the model.
This representation addresses a narrow range of use cases. It has limited potential for customization and performance. It is more difficult to use because it excludes the start line fields from the model.
06/05/2026
Browse all string changes

Glossary

English Chinese (Simplified Han script)
No related strings found in the glossary.

String information

Source string description
type: paragraph
Unit identifier
58650
Source string location
string ID 228
String age
06/05/2026
Last updated
06/26/2026
Source string age
06/05/2026
Translation file QuickBook file
doc/qbk/08_design/2_http_comparison_zh_Hans.qbk, string 35