msgid "" msgstr "" "Project-Id-Version: Chinese (Simplified Han script) (Boost Beast Translation " "(zh_Hans))\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2026-06-07 16:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: Chinese (Simplified Han script) \n" "Language: zh_Hans\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Weblate 2026.5\n" #. type: section title #: 10 #, fuzzy msgid "Detect SSL __example__" msgstr "Detect SSL __example__" #. type: paragraph #: 12 #, fuzzy msgid "" "In this example we will build a simple function to detect the presence of " "the [@https://tools.ietf.org/html/rfc2246#section-7.4 TLS client handshake] " "given an input buffer sequence. Then we build on the example by adding a " "synchronous stream algorithm. Finally, we implement an asynchronous " "detection function using a composed operation. This SSL detector may be used " "to allow a server to accept both TLS and plain (unencrypted) connections at " "the same port." msgstr "" "In this example we will build a simple function to detect the presence of " "the [@https://tools.ietf.org/html/rfc2246#section-7.4 TLS client handshake] " "given an input buffer sequence. Then we build on the example by adding a " "synchronous stream algorithm. Finally, we implement an asynchronous " "detection function using a composed operation. This SSL detector may be used " "to allow a server to accept both TLS and plain (unencrypted) connections at " "the same port." #. type: paragraph #: 20 #, fuzzy msgid "" "Here is the declaration for a function template to detect the SSL client " "handshake. The function accepts any object whose type meets the requirements " "of __ConstBufferSequence__. This gives callers flexibility to use a buffer " "object whose behavior is appropriate to the task." msgstr "" "Here is the declaration for a function template to detect the SSL client " "handshake. The function accepts any object whose type meets the requirements " "of __ConstBufferSequence__. This gives callers flexibility to use a buffer " "object whose behavior is appropriate to the task." #. type: paragraph #: 27 #, fuzzy msgid "" "The algorithm examines the buffer starting from the beginning, and performs " "a series of qualifying checks against the TLS specification. When not enough " "data exists to be certain, the returned value of `boost::indeterminate` " "informs the caller to read more data into the buffer. The function " "definition for the declaration above follows:" msgstr "" "The algorithm examines the buffer starting from the beginning, and performs " "a series of qualifying checks against the TLS specification. When not enough " "data exists to be certain, the returned value of `boost::indeterminate` " "informs the caller to read more data into the buffer. The function " "definition for the declaration above follows:" #. type: paragraph #: 35 #, fuzzy msgid "" "The detection function above is suitably generic and targeted in focus that " "it may be used as a building block to create higher level abstractions. Our " "goal is to create a ['stream algorithm]: a function which is invoked with a " "stream, that reads or writes (or both) to achieve a purpose. In this case, " "to detect the TLS client handshake. Stream algorithms may be synchronous or " "asynchronous. Because synchronous algorithms are easier to write, we start " "there. Then we build the asynchronous version, trying to model it similarly " "to make reasoning about it easier." msgstr "" "The detection function above is suitably generic and targeted in focus that " "it may be used as a building block to create higher level abstractions. Our " "goal is to create a ['stream algorithm]: a function which is invoked with a " "stream, that reads or writes (or both) to achieve a purpose. In this case, " "to detect the TLS client handshake. Stream algorithms may be synchronous or " "asynchronous. Because synchronous algorithms are easier to write, we start " "there. Then we build the asynchronous version, trying to model it similarly " "to make reasoning about it easier." #. type: paragraph #: 44 #, fuzzy msgid "The synchronous version is implemented thusly:" msgstr "The synchronous version is implemented thusly:" #. type: paragraph #: 48 #, fuzzy msgid "" "Now that we have the synchronous version, we can attempt to model the " "asynchronous version similarly. A function which launches an asynchronous " "operation is called an ['initiating function]. While the synchronous " "version above produces an error code through an output parameter, the " "asynchronous version delivers the error code to a completion handler or " "other custom mechanism defined by the completion token. The signature of the " "initiating function reflects these differences." msgstr "" "Now that we have the synchronous version, we can attempt to model the " "asynchronous version similarly. A function which launches an asynchronous " "operation is called an ['initiating function]. While the synchronous " "version above produces an error code through an output parameter, the " "asynchronous version delivers the error code to a completion handler or " "other custom mechanism defined by the completion token. The signature of the " "initiating function reflects these differences." #. type: paragraph #: 56 #, fuzzy msgid "" "First we declare the initiating function and document the requirements, " "parameters, preconditions, and effects:" msgstr "" "First we declare the initiating function and document the requirements, " "parameters, preconditions, and effects:" #. type: paragraph #: 61 #, fuzzy msgid "" "There are two additional components required to implement the initiating " "function:" msgstr "" "There are two additional components required to implement the initiating " "function:" #. type: list #: 64 #, fuzzy msgid "* An intermediate completion handler, called the \"composed operation\"" msgstr "* An intermediate completion handler, called the \"composed operation\"" #. type: list #: 69 #, fuzzy msgid "* An \"initiation\" function object which when invoked with parameters" msgstr "* An \"initiation\" function object which when invoked with parameters" #. type: paragraph #: 73 #, fuzzy msgid "" "Here we forward declare the composed operation type, and provide the " "definition of the initiation function object. They are placed in the " "`detail` namespace since they should not be public:" msgstr "" "Here we forward declare the composed operation type, and provide the " "definition of the initiation function object. They are placed in the " "`detail` namespace since they should not be public:" #. type: paragraph #: 79 #, fuzzy msgid "" "The initiating function definition itself is straightforward. We perform " "type checking on the parameters, and then let `net::async_initiate` capture " "the parameter list along with a copy of our initiation function object. " "Depending on the specialization of `async_result` for the type of " "`CompletionToken`, the initiation function may be invoked immediately. " "Alternatively, it may be invoked later, after the initiating function " "returns. This is known as \"lazy execution,\" and allows efficient and " "expressive abstractions to be written." msgstr "" "The initiating function definition itself is straightforward. We perform " "type checking on the parameters, and then let `net::async_initiate` capture " "the parameter list along with a copy of our initiation function object. " "Depending on the specialization of `async_result` for the type of " "`CompletionToken`, the initiation function may be invoked immediately. " "Alternatively, it may be invoked later, after the initiating function " "returns. This is known as \"lazy execution,\" and allows efficient and " "expressive abstractions to be written." #. type: paragraph #: 90 #, fuzzy msgid "" "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." msgstr "" "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." #. type: paragraph #: 96 #, fuzzy msgid "" "The boilerplate is all done, and now we need to implement the function call " "operator that turns this composed operation a completion handler with the " "signature `void(error_code, std::size_t)` which is exactly the signature " "needed when performing asynchronous reads. This function is a transformation " "of the synchronous version of `detect_ssl` above, but with the inversion of " "flow that characterizes code written in the callback style:" msgstr "" "The boilerplate is all done, and now we need to implement the function call " "operator that turns this composed operation a completion handler with the " "signature `void(error_code, std::size_t)` which is exactly the signature " "needed when performing asynchronous reads. This function is a transformation " "of the synchronous version of `detect_ssl` above, but with the inversion of " "flow that characterizes code written in the callback style:" #. type: paragraph #: 106 #, fuzzy msgid "" "The examples [path_link example/advanced/server/advanced_server.cpp advanced-" "server] and [path_link example/advanced/server-flex/advanced_server_flex.cpp " "advanced-server-flex] use this SSL detection function." msgstr "" "The examples [path_link example/advanced/server/advanced_server.cpp advanced-" "server] and [path_link example/advanced/server-flex/advanced_server_flex.cpp " "advanced-server-flex] use this SSL detection function."