Boost Beast Translation (zh_Hans) - English @ Boost-Weblate

Exit Zen

14 string ID 30
	Source string description type: table cell

	English `B::reader` 11/10000 · 11
14 string ID 36
	Source string description type: table cell

	English A type which meets the requirements of __FieldsWriter__. 56/10000 · 56
14 string ID 49
	Source string description type: table cell

	English Type 4/10000 · 4
14 string ID 45
	Source string description type: table cell

	English Semantics, Pre/Post-conditions 30/10000 · 30
14 string ID 50
	Source string description type: table cell

	English Semantics, Pre/Post-conditions 30/10000 · 30
14 string ID 93
	Source string description type: list

	English * No stateful allocator support. 32/10000 · 32
14 string ID 16
	Source string description type: variablelist cell

	English The name "Boost.Http" or "Boost.WebSocket" would mislead users into believing they could perform an HTTP request on a URL or put up a WebSocket client or server in a couple of lines of code. Where would the core utilities go? Very likely it would step on the owner of Boost.Asio's toes to put things in the boost/asio directory; at the very least, it would create unrequested, additional work for the foreign repository. "Beast" is sufficiently vague as to not suggest any particular functionality, while acting as a memorable umbrella term for a family of low level containers and algorithms. People in the know or with a need for low-level network protocol operations will have no trouble finding it, and the chances of luring a novice into a bad experience are greatly reduced. There is precedent for proper names: "Hana", "Fusion", "Phoenix", and "Spirit" come to mind. Is "Beast" really any worse than say, "mp11" for example? Beast also already has a growing body of users and attention from the open source community, the name Beast comes up in reddit posts and StackOverflow as the answer to questions about which HTTP or WebSocket library to use. 1156/10000 · 1156
14 string ID 55
	Source string description type: paragraph

	English The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed). 193/10000 · 193
14 string ID 105
	Source string description type: paragraph

	English However, a problem arises. How do we write a function which can accept an object that is either a request or a response? As written, the only obvious solution is to make the message a template type. Additional traits classes would then be needed to make sure that the passed object has a valid type which meets the requirements. These unnecessary complexities are bypassed by making each container a partial specialization: ``` /// An HTTP message template<bool isRequest, class Fields, class Body> struct message; 514/10000 · 514
14 string ID 57
	Source string description type: paragraph

	English Beast requires: 15/10000 · 15
14 string ID 21
	Source string description type: table cell

	English [link beast.ref.boost__beast__buffers_prefix `buffers_prefix`] 62/10000 · 62
14 string ID 92
	Source string description type: paragraph

	English The function [@boost:/doc/html/boost_asio/reference/make_strand.html `make_strand`] returns a strand constructed from an execution context or executor. When a [@boost:/doc/html/boost_asio/reference/strand.html `net::strand`] is chosen for the stream's executor, all completion handlers which do not already have an associated executor will use the strand. This is both a notational convenience (no need for `strand::wrap` or `bind_executor` at call sites) and a measure of safety, as it is no longer possible to forget to use the strand. 537/10000 · 537
14 string ID 72
	Source string description type: heading

	English Client Certificate 18/10000 · 18
14 string ID 44
	Source string description type: table cell

	English [link beast.ref.boost__beast__bind_front_handler `bind_front_handler`] 70/10000 · 70
14 string ID 63
	Source string description type: paragraph

	English Boost.Beast depends specifically on the Boost.Asio flavor of Networking, although this may change in the future. While this library offers performant implementations of the HTTP and WebSocket network protocols, it depends on the networking interfaces to perform general tasks such as performing domain name resolution (DNS lookup), establishing outgoing connections, and accepting incoming connections. Callers are responsible for interacting with networking to initialize objects to the correct state where they are usable by this library. 540/10000 · 540
14 string ID 46
	Source string description type: table cell

	English [link beast.ref.boost__beast__close_socket `close_socket`] 58/10000 · 58
14 string ID 148
	Source string description type: paragraph

	English Synchronous input and output is accomplished through blocking function calls that return with the result of the operation. Such operations typically cannot be canceled and do not have a method for setting a timeout. The __SyncReadStream__ and __SyncWriteStream__ concepts define requirements for ['synchronous streams]: a portable I/O abstraction that transfers data using buffer sequences to represent bytes and either `error_code` or an exception to report any failures. [@boost:/doc/html/boost_asio/reference/basic_stream_socket.html ['net::basic_stream_socket]] is a synchronous stream commonly used to form TCP/IP connections. User-defined types which meet the requirements are possible: 692/10000 · 692
14 string ID 21
	Source string description type: table cell

	English __AsyncWriteStream__ 20/10000 · 20
14 string ID 90
	Source string description type: paragraph

	English Now we will declare our composed operation. There is a considerable amount of necessary boilerplate to get this right, but the result is worth the effort. 154/10000 · 154
14 string ID 25
	Source string description type: table cell

	English [path_link example/http/client/async-ssl-system-executor/http_client_async_ssl_system_executor.cpp http_client_async_ssl_system_executor.cpp] 141/10000 · 141

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.