mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-15 16:38:54 +00:00
remove the incorrect use of the word parallel from curl_multi_* documentation
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@335160 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
3c735d9bbc
commit
b653253e42
5 changed files with 6 additions and 7 deletions
|
@ -44,7 +44,7 @@
|
|||
<title><function>curl_multi_add_handle</function> example</title>
|
||||
<para>
|
||||
This example will create two cURL handles, add them to a multi
|
||||
handle, and then run them in parallel.
|
||||
handle, and process them asynchronously.
|
||||
</para>
|
||||
<programlisting role="php">
|
||||
<![CDATA[
|
||||
|
|
|
@ -40,7 +40,7 @@
|
|||
<title><function>curl_multi_close</function> example</title>
|
||||
<para>
|
||||
This example will create two cURL handles, add them to a multi
|
||||
handle, and then run them in parallel.
|
||||
handle, and process them asynchronously.
|
||||
</para>
|
||||
<programlisting role="php">
|
||||
<![CDATA[
|
||||
|
|
|
@ -57,7 +57,7 @@
|
|||
<title><function>curl_multi_exec</function> example</title>
|
||||
<para>
|
||||
This example will create two cURL handles, add them to a multi
|
||||
handle, and then run them in parallel.
|
||||
handle, and process them asynchronously.
|
||||
</para>
|
||||
<programlisting role="php">
|
||||
<![CDATA[
|
||||
|
|
|
@ -13,7 +13,7 @@
|
|||
<void />
|
||||
</methodsynopsis>
|
||||
<para>
|
||||
Allows the processing of multiple cURL handles in parallel.
|
||||
Allows the processing of multiple cURL handles asynchronously.
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
|
@ -36,7 +36,7 @@
|
|||
<title><function>curl_multi_init</function> example</title>
|
||||
<para>
|
||||
This example will create two cURL handles, add them to a multi
|
||||
handle, and then run them in parallel.
|
||||
handle, and process them asynchronously.
|
||||
</para>
|
||||
<programlisting role="php">
|
||||
<![CDATA[
|
||||
|
|
|
@ -67,8 +67,7 @@
|
|||
handle will make it attempt to perform HTTP Pipelining as far as
|
||||
possible for transfers using this handle. This means that if you add
|
||||
a second request that can use an already existing connection, the
|
||||
second request will be "piped" on the same connection rather than
|
||||
being executed in parallel.
|
||||
second request will be "piped" on the same connection.
|
||||
</entry>
|
||||
</row>
|
||||
<row>
|
||||
|
|
Loading…
Reference in a new issue