Consider changing the default HTTPConduitFactory to HttpClientHTTPConduitFactory

[ppalaga]

We can do this in the next major or minor release, once #1090 is merged.

It would be nice to run some perf benchmarks using URLConnectionHTTPConduitFactory and HttpClientHTTPConduitFactory.

Possible topics to cover:

• Small/large payloads
• http vs. https

[ppalaga]

I need to figure out whether https://issues.apache.org/jira/projects/CXF/issues/CXF-8951 has any relevance to us. Although it is about JAX-RS clients, the way how the HTTP clients are managed by the two conduit implementations might be the same for JAX-WS clients.

[famod]

Just FWIW, for each QCXF update in my app I'm re-checking #971 (reply in thread) and so far nothing has changed.
That's also why we pinned URLConnectionHTTPConduitFactory via config to avoid nasty surprises on a QCXF update.
Sadly, I haven't had time to take a stab at a reproducer (with and without Quarkus in the mix).

[ppalaga]

Just FWIW, for each QCXF update in my app I'm re-checking #971 (reply in thread) and so far nothing has changed. That's also why we pinned URLConnectionHTTPConduitFactory via config to avoid nasty surprises on a QCXF update. Sadly, I haven't had time to take a stab at a reproducer (with and without Quarkus in the mix).

I think it would be worth to track this as a separate issue. At least there is a clear and easy way to reproduce. Would you mind filing a new issue?