Boost Beast Translation (zh_Hans)/Doc / Qbk / 08 Design / 2 Http Comparison (qbk) — Chinese (Simplified Han script) @ Boost-Weblate: is a library resulting from the 2014 Google Summer of …

Zen

Translation

Source string description

type: paragraph

English

Chinese (Simplified Han script)

Needs editing (Needs rewriting)

Skip

Loading…

admin

String added in the repository

English

Chinese (Simplified Han script) 347 characters editedCurrent translationState: Needs editing (Needs rewriting)

06/05/2026

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical.

Reset

Glossary

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

String information

Source string description

type: paragraph

Unit identifier

58638

Source string location

string ID 143

String age

06/05/2026

Last updated

06/05/2026

Source string age

06/05/2026

Translation file QuickBook file

doc/qbk/08_design/2_http_comparison_zh_Hans.qbk, string 23

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the previous translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.

Key	English	Chinese (Simplified Han script)
	Declarations examples from external libraries have been edited:	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 {	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 {
82	}; ```	}; ```
	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:	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:
	* The header and body containers may only be default-constructed.	* The header and body containers may only be default-constructed.
	* No stateful allocator support.	* No stateful allocator support.
	* There is no way to defer the commitment of the type for `body_` to	* There is no way to defer the commitment of the type for `body_` to
	* The message model includes a "source" and "destination." This is	* The message model includes a "source" and "destination." This is
	* The use of `string_type` (a customization point) for source,	* The use of `string_type` (a customization point) for source,
	* The library uses specializations of `string<Tag>` to change the type	* The library uses specializations of `string<Tag>` to change the type
	* The specialized trait classes generate a proliferation of small	* The specialized trait classes generate a proliferation of small
	* The `string<Tag> customization point constrains user defined body types	* The `string<Tag> customization point constrains user defined body types
	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.	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.
	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 {	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 {
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	* This container cannot model a complete message. The ['start-line] items
	* `headers_`, `body_`, and `trailers_` may only be default-constructed,	* `headers_`, `body_`, and `trailers_` may only be default-constructed,
	* There is no way to defer the commitment of the [*Body] type to after	* There is no way to defer the commitment of the [*Body] type to after
	* No stateful allocator support. This follows from the previous limitation	* No stateful allocator support. This follows from the previous limitation
	* The trailers are stored in a separate object. Aside from the combinatorial	* The trailers are stored in a separate object. Aside from the combinatorial
	* The declarations imply that `std::vector` is a model of [*Body].	* The declarations imply that `std::vector` is a model of [*Body].
	* The [*Body] customization point constrains user defined types to	* The [*Body] customization point constrains user defined types to
	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.
	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.	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.
	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:	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:

	English	Chinese (Simplified Han script)	Actions
	* 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
	* Setting the body requires either a vector or a `concurrency::streams::istream`.	* Setting the body requires either a vector or a `concurrency::streams::istream`.
	* The HTTP request container conflates HTTP response behavior (see the	* The HTTP request container conflates HTTP response behavior (see the
	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.
	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:	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:
	* The header and body containers may only be default-constructed.	* The header and body containers may only be default-constructed.
	* No stateful allocator support.	* No stateful allocator support.
	* There is no way to defer the commitment of the type for `body_` to	* There is no way to defer the commitment of the type for `body_` to
	* The message model includes a "source" and "destination." This is	* The message model includes a "source" and "destination." This is
	* The use of `string_type` (a customization point) for source,	* The use of `string_type` (a customization point) for source,
	* The library uses specializations of `string<Tag>` to change the type	* The library uses specializations of `string<Tag>` to change the type
	* The specialized trait classes generate a proliferation of small	* The specialized trait classes generate a proliferation of small
	* The `string<Tag> customization point constrains user defined body types	* The `string<Tag> customization point constrains user defined body types
	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.	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.
	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 {	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 {
	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	* This container cannot model a complete message. The ['start-line] items
	* `headers_`, `body_`, and `trailers_` may only be default-constructed,	* `headers_`, `body_`, and `trailers_` may only be default-constructed,
	* There is no way to defer the commitment of the [*Body] type to after	* There is no way to defer the commitment of the [*Body] type to after
	* No stateful allocator support. This follows from the previous limitation	* No stateful allocator support. This follows from the previous limitation
	* The trailers are stored in a separate object. Aside from the combinatorial	* The trailers are stored in a separate object. Aside from the combinatorial
	* The declarations imply that `std::vector` is a model of [*Body].	* The declarations imply that `std::vector` is a model of [*Body].
	* The [*Body] customization point constrains user defined types to	* The [*Body] customization point constrains user defined types to
	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.
	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.	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.
	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:	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:
	This declaration is quite bare-bones. We note the typical problems of most field containers:	This declaration is quite bare-bones. We note the typical problems of most field containers:

Translation

Things to check

Unchanged translation

Glossary

String information

Source string description

Details

Unit identifier

Source string location

String age

Last updated

Source string age

Translation file QuickBook file