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

2 string ID 12
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 201/10000 · 201
3 string ID 16
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The general strategy used by the author to evaluate external libraries is as follows: 85/10000 · 85
4 string ID 19
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * Review the message model. Can it represent a complete request or 66/10000 · 66
5 string ID 23
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * Review the stream abstraction. This is the type of object, such as 68/10000 · 68
6 string ID 28
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * Check treatment of buffers. Does the library manage the buffers 65/10000 · 65
7 string ID 31
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * How does the library handle corner cases such as trailers, 60/10000 · 60
8 string ID 35
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Declarations examples from external libraries have been edited: 63/10000 · 63
9 string ID 41
	Source string description type: heading
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — cpp-netlib 10/10000 · 10
10 string ID 44
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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 { 604/10000 · 604
82 string ID 82
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — }; ``` 6/10000 · 6
12 string ID 85
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — This container is the base class template used to represent HTTP messages. It uses a "tag" type style specializations for a variety of trait classes, allowing for customization of the various parts of the message. For example, a user specializes `headers_container<T>` to determine what container type holds the header fields. We note some problems with the container declaration: 380/10000 · 380
13 string ID 91
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The header and body containers may only be default-constructed. 65/10000 · 65
14 string ID 93
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * No stateful allocator support. 32/10000 · 32
15 string ID 95
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * There is no way to defer the commitment of the type for `body_` to 68/10000 · 68
16 string ID 98
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The message model includes a "source" and "destination." This is 66/10000 · 66
17 string ID 102
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The use of `string_type` (a customization point) for source, 62/10000 · 62
18 string ID 112
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The library uses specializations of `string<Tag>` to change the type 70/10000 · 70
19 string ID 121
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The specialized trait classes generate a proliferation of small 65/10000 · 65
20 string ID 127
	Source string description type: list
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — * The `string<Tag> customization point constrains user defined body types 73/10000 · 73
21 string ID 132
	Source string description type: paragraph
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 303/10000 · 303