2. Boost Beast Translation (zh_Hans)
3. Doc / Qbk / 08 Design / 1 Http Message (qbk)
4. Chinese (Simplified Han script)
5. Zen

46 string ID 335
	Source string description type: paragraph
	English /// An HTTP response template<class Body, class Fields = fields> using response = message<false, Body, Fields>; ```
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — /// An HTTP response template<class Body, class Fields = fields> using response = message<false, Body, Fields>; ``` 115/1150 · 115 Needs editing (Needs rewriting)
47 string ID 340
	Source string description type: paragraph
	English This allows concise specification for the common cases, while allowing for maximum customization for edge cases: ``` request<string_body> req;
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — This allows concise specification for the common cases, while allowing for maximum customization for edge cases: ``` request<string_body> req; 142/1420 · 142 Needs editing (Needs rewriting)
48 string ID 345
	Source string description type: paragraph
	English response<file_body> res; ```
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — response<file_body> res; ``` 28/280 · 28 Needs editing (Needs rewriting)
49 string ID 348
	Source string description type: paragraph
	English This container is also capable of representing complete HTTP/2 messages. Not because it was explicitly designed for, but because the IETF wanted to preserve message compatibility with HTTP/1. Aside from version specific fields such as Connection, the contents of HTTP/1 and HTTP/2 messages are identical even though their serialized representation is considerably different. The message model presented in this library is ready for HTTP/2.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — This container is also capable of representing complete HTTP/2 messages. Not because it was explicitly designed for, but because the IETF wanted to preserve message compatibility with HTTP/1. Aside from version specific fields such as Connection, the contents of HTTP/1 and HTTP/2 messages are identical even though their serialized representation is considerably different. The message model presented in this library is ready for HTTP/2. 439/4390 · 439 Needs editing (Needs rewriting)
50 string ID 355
	Source string description type: paragraph
	English In conclusion, this representation for the message container is well thought out, provides comprehensive flexibility, and avoids the necessity of defining additional traits classes. User declarations of functions that accept headers or messages as parameters are easy to write in a variety of ways to accomplish different results, without forcing cumbersome SFINAE declarations everywhere.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — In conclusion, this representation for the message container is well thought out, provides comprehensive flexibility, and avoids the necessity of defining additional traits classes. User declarations of functions that accept headers or messages as parameters are easy to write in a variety of ways to accomplish different results, without forcing cumbersome SFINAE declarations everywhere. 389/3890 · 389 Needs editing (Needs rewriting)
The translation has come to an end.