| commit | 5636d41ba5c15a53d3851f64651f657a0f40785b | [log] [tgz] |
|---|---|---|
| author | David Pursehouse <david.pursehouse@sonymobile.com> | Wed May 27 12:16:55 2015 +0900 |
| committer | David Pursehouse <david.pursehouse@sonymobile.com> | Thu May 28 17:15:36 2015 +0900 |
| tree | 5b1bc207b0c573d914b6aca744cf2755302558e1 | |
| parent | 1a9353c33ac088766811a0d992196c4739127619 [diff] |
Use httpcomponents fluent API in acceptance tests By using the fluent API we can simplify the HTTP connection calls. We no longer need to explicitly set the max connections per route and max total connections. Internally the fluent API's Executor [1] uses a PoolingHttpClientConnectionManager with maximum 100 connections per route and a total maximum of 200 connections. These maximums are not as high as the ones we were previously using, but those were most likely over-estimated anyway. [1] http://hc.apache.org/httpcomponents-client-ga/fluent-hc/apidocs/org/apache/http/client/fluent/Executor.html Change-Id: Ibab7ff76736f9ba063df28addc9a786bbaaadfe7