User avatar None

Resource updated
Parsing of the “doc/qbk/08_design/2_http_comparison_zh_Hans.qbk” file was enforced. 06/26/2026
User avatar Bstran

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

Translation changed
Tasks in the Concurrency Runtime operate in a fashion similar to `std::future`, but with some improvements such as continuations which are not yet in the C++ standard. The costs of using a task based asynchronous interface instead of completion handlers is well documented: synchronization points along the call chain of composed task operations which cannot be optimized away. See: [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3747.pdf [*A Universal Model for Asynchronous Operations]] (Kohlhoff).
Tasks in the Concurrency Runtime operate in a fashion similar to `std::future`, but with some improvements such as continuations which are not yet in the C++ standard. The costs of using a task based asynchronous interface instead of completion handlers is well documented: synchronization points along the call chain of composed task operations which cannot be optimized away. See: 中的任务操作方式与 `std::future` 类似，但进行了一些改进，例如 C++ 标准中尚未包含的 continuation（续体）。使用基于任务的异步接口而非完成处理程序（completion handlers）的代价已有详细记录：在组合任务操作的调用链上存在无法优化的同步点。参见：[@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3747.pdf [*A Universal Model for Asynchronous Operations]] (Kohlhoff).。
06/20/2026
User avatar Bstran

Translation changed
The general theme of the HTTP message model in cpprestsdk is "no user definable customizations". There is no allocator support, and no separation of concerns. It is designed to perform a specific set of behaviors. In other words, it does not follow the open/closed principle.
The general theme of the HTTP message model in cpprestsdk is "no user definable customizations". There is no allocator support, and no separation of concerns. It is designed to perform a specific set of behaviors. In other words, it does not follow the open/closed principle.cpprestsdk 中 HTTP 消息模型的总体主题是“不支持用户可定义的自定义功能”。它没有分配器支持，也没有关注点分离。它的设计目的是执行特定的行为集。换句话说，它没有遵循开闭原则。
06/20/2026
User avatar Bstran

Translation changed
* The HTTP request container conflates HTTP response behavior (see the
* The HTTP request container conflates HTTP response behavior (see the请求容器混淆了 HTTP 响应行为（见
06/20/2026
User avatar Bstran

Translation changed
* Setting the body requires either a vector or a `concurrency::streams::istream`.
* Setting the body requires either a vector or a设置消息体需要使用向量或 `concurrency::streams::istream`.。
06/20/2026
User avatar Bstran

Translation changed
* A body can only be extracted once, limiting the use of this container
* A body can only be extracted once, limiting the use of this container消息体只能提取一次，这限制了该容器的使用
06/20/2026
User avatar Bstran

Translation changed
* No way to define an allocator for the container used when extracting
* No way to define an allocator for the container used when extracting无法为提取数据时所使用的容器定义分配器
06/20/2026
User avatar Bstran

Translation changed
* The extraction of the body is conflated with the asynchronous model.
* The extraction of the body is conflated with the asynchronous model.消息体的提取与异步模型混为一谈。
06/20/2026
User avatar Bstran

Translation changed
* There are no compile-time customization points at all. The only
* There are no compile-time customization points at all. The only完全没有编译期自定义点。唯一
06/20/2026
User avatar Bstran

Translation changed
It is clear from this declaration that the goal of the message model in this library is driven by its use-case (interacting with REST servers) and not to model HTTP messages generally. We note problems similar to the other declarations:
It is clear from this declaration that the goal of the message model in this library is driven by its use-case (interacting with REST servers) and not to model HTTP messages generally. We note problems similar to the other declarations:从这个声明中可以清楚地看出，该库中消息模型的目标是由其用例（与 REST 服务器交互）驱动的，而不是为了对 HTTP 消息进行通用建模。我们注意到存在与其他声明类似的问题：
06/20/2026
User avatar Bstran

Translation changed
}; ```
}; ```
412
06/20/2026
User avatar Bstran

Translation changed
private:
private:
407
06/20/2026
User avatar Bstran

Translation changed
Finally, here is the public class which represents an HTTP request: ``` class http_request { public:
Finally, here is the public class which represents an HTTP request: 最后，下面是代表 HTTP 请求的公共类：``` class http_request { public:
06/20/2026
User avatar Bstran

Translation changed
* The `_reply_impl` function implies that the message implementation also
* The `_reply_impl` function implies that the message implementation also函数意味着消息的实现也
06/20/2026
User avatar Bstran

Translation changed
* The "cancellation token" is stored inside the message. This breaks the
* The "cancellation token" is stored inside the message. This breaks the“取消令牌”被存储在消息内部。这破坏了
06/20/2026
User avatar Bstran

Translation changed
* The constructor accepting `std::unique_ptr<http::details::_http_server_context`
* The constructor accepting接受 `std::unique_ptr<http::details::_http_server_context` 的构造函数
06/20/2026
User avatar Bstran

Translation changed
As before, we note that the implementation class for HTTP requests concerns itself more with the mechanics of sending the message asynchronously than it does with actually modeling the HTTP message as described in __rfc7230__:
As before, we note that the implementation class for HTTP requests concerns itself more with the mechanics of sending the message asynchronously than it does with actually modeling the HTTP message as described in __rfc7230__:与之前一样，可以看出，HTTP 请求的实现类更关注于异步发送消息的机制，而不是按照 __rfc7230__ 中的描述对 HTTP 消息进行实际建模：
06/20/2026
User avatar Bstran

Translation changed
} // namespace details ```
} // namespace details ```
06/20/2026
User avatar Bstran

Translation changed
};
};
344
06/20/2026

Search