<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 11/18/19 4:03 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DF3AF860-1032-4B5E-8F7D-A3854FC9C660@osu.edu">
<pre class="moz-quote-pre" wrap="">On 11/18/19, 2:39 PM, "dev on behalf of Jim Fox" <a class="moz-txt-link-rfc2396E" href="mailto:dev-bounces@shibboleth.netonbehalfoffox@washington.edu"><dev-bounces@shibboleth.net on behalf of fox@washington.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I'm curious why the HttpClient (v3.4) is implemented as a
singleton, rather than, say, from a PoolingHttpClientConnectionManager.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Brent would know better than I, but I don't think it is. We don't install our own ConnectionManager from what I can see, which means it auto-installs a PoolingHttpClientConnectionManager, and that's why the builder we have exposes properties like max connections and max per-route.
It's all a bit spaghetti, but that's how it read to me. I think I've tested that in the past and certainly seen it operate multiple connections at a time.</pre>
</blockquote>
<p><br>
</p>
<p>Yes, that's correct as far as I know. The Apache builder, which
our builder wraps, defaults to a
PoolingHttpClientConnectionManager, so that's what you get by
default.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:DF3AF860-1032-4B5E-8F7D-A3854FC9C660@osu.edu">
<pre class="moz-quote-pre" wrap="">
The TLS layer adds a lot of complexity to what we're doing, but I think all that is being done outside the scope of actually overriding its connection manager.</pre>
</blockquote>
<p><br>
</p>
<p>Yes, I don't think that changes the connection manager you get,
just the TLS socket factory. So you'll still get the pooling conn
mgr.<br>
</p>
<br>
</body>
</html>