curl/tests/data/test1900

<testcase>
<info>
<keywords>
HTTP
pipelining
multi
</keywords>
</info>

# Server-side
<reply>
<data>
Adding handle 0
Handle 0 Completed with status 0
Adding handle 1
Adding handle 2
Adding handle 3
Adding handle 4
Adding handle 5
Adding handle 6
Handle 4 Completed with status 0
Handle 5 Completed with status 0
Handle 6 Completed with status 0
Handle 1 Completed with status 0
Handle 2 Completed with status 0
Handle 3 Completed with status 0
</data>
</reply>

# Client-side
<client>
<server>
http-pipe
</server>
<tool>
lib1900
</tool>
 <name>
HTTP GET using pipelining
 </name>
 <command>
http://%HOSTIP:%HTTPPIPEPORT/
</command>
<file name="log/urls.txt">
0 1k.txt
1000 100k.txt
0 1k.txt
0 1k.txt
0 1k.txt
0 1k.txt
0 1k.txt
</client>

# Verify data after the test has been "shot"
<verify>
</verify>
</testcase>
Multiple pipelines and limiting the number of connections. Introducing a number of options to the multi interface that allows for multiple pipelines to the same host, in order to optimize the balance between the penalty for opening new connections and the potential pipelining latency. Two new options for limiting the number of connections: CURLMOPT_MAX_HOST_CONNECTIONS - Limits the number of running connections to the same host. When adding a handle that exceeds this limit, that handle will be put in a pending state until another handle is finished, so we can reuse the connection. CURLMOPT_MAX_TOTAL_CONNECTIONS - Limits the number of connections in total. When adding a handle that exceeds this limit, that handle will be put in a pending state until another handle is finished. The free connection will then be reused, if possible, or closed if the pending handle can't reuse it. Several new options for pipelining: CURLMOPT_MAX_PIPELINE_LENGTH - Limits the pipeling length. If a pipeline is "full" when a connection is to be reused, a new connection will be opened if the CURLMOPT_MAX_xxx_CONNECTIONS limits allow it. If not, the handle will be put in a pending state until a connection is ready (either free or a pipe got shorter). CURLMOPT_CONTENT_LENGTH_PENALTY_SIZE - A pipelined connection will not be reused if it is currently processing a transfer with a content length that is larger than this. CURLMOPT_CHUNK_LENGTH_PENALTY_SIZE - A pipelined connection will not be reused if it is currently processing a chunk larger than this. CURLMOPT_PIPELINING_SITE_BL - A blacklist of hosts that don't allow pipelining. CURLMOPT_PIPELINING_SERVER_BL - A blacklist of server types that don't allow pipelining. See the curl_multi_setopt() man page for details. 2013-02-15 05:50:45 -05:00			`<testcase>`
			`<info>`
			`<keywords>`
			`HTTP`
			`pipelining`
			`multi`
			`</keywords>`
			`</info>`

			`# Server-side`
			`<reply>`
			`<data>`
			`Adding handle 0`
			`Handle 0 Completed with status 0`
			`Adding handle 1`
			`Adding handle 2`
			`Adding handle 3`
			`Adding handle 4`
			`Adding handle 5`
			`Adding handle 6`
			`Handle 4 Completed with status 0`
			`Handle 5 Completed with status 0`
			`Handle 6 Completed with status 0`
			`Handle 1 Completed with status 0`
			`Handle 2 Completed with status 0`
			`Handle 3 Completed with status 0`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`http-pipe`
			`</server>`
			`<tool>`
			`lib1900`
			`</tool>`
			`<name>`
			`HTTP GET using pipelining`
			`</name>`
			`<command>`
			`http://%HOSTIP:%HTTPPIPEPORT/`
			`</command>`
			`<file name="log/urls.txt">`
			`0 1k.txt`
			`1000 100k.txt`
			`0 1k.txt`
			`0 1k.txt`
			`0 1k.txt`
			`0 1k.txt`
			`0 1k.txt`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`</verify>`
			`</testcase>`