2. Boost Beast Translation (zh_Hans)
3. Doc / Qbk / 08 Design / 2 Http Comparison (qbk)
4. English
5. Zen

56 string ID 357
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The "cancellation token" is stored inside the message. This breaks the 72/10000 · 72
57 string ID 360
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The `_reply_impl` function implies that the message implementation also 73/10000 · 73
58 string ID 364
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Finally, here is the public class which represents an HTTP request: ``` class http_request { public: 100/10000 · 100
407 string ID 407
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — private: 8/10000 · 8
412 string ID 412
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — }; ``` 6/10000 · 6
61 string ID 415
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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: 236/10000 · 236
62 string ID 420
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * There are no compile-time customization points at all. The only 65/10000 · 65
63 string ID 426
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The extraction of the body is conflated with the asynchronous model. 70/10000 · 70
64 string ID 428
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * No way to define an allocator for the container used when extracting 70/10000 · 70
65 string ID 431
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * A body can only be extracted once, limiting the use of this container 71/10000 · 71
66 string ID 434
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * Setting the body requires either a vector or a `concurrency::streams::istream`. 81/10000 · 81
67 string ID 437
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The HTTP request container conflates HTTP response behavior (see the 70/10000 · 70
68 string ID 442
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 275/10000 · 275
69 string ID 447
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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). 512/10000 · 512
The translation has come to an end.