[Jetty-support] jetty http clinet - creates lots of threads

[Adam M. <ad...@cs...>]

Hi,

New to Jetty, I am looking for a lightweight non-blocking httpClient that
does not use an individual thread per HTTP client request, and uses an
async call-back.

If I understood the docs correctly, the Jetty HttpClient should do this, as
it is NIO and async api.

So, I created an example where I fired off 40 requests (using the async
api), and before the results came back I printed all the threads in the
jvm.  There were about 28 threads of the title "HttpClient@127419417..."
Wow, I have almost as many threads as requests.  (Note I used the same
httpClient instance).

Is this the expected behavior of the http client?

Thanks,

-Adam