users@jersey.java.net

Non-blocking client without Jersey's thread pool

From: Grenville Wilson <grenvillevcwilson_at_gmail.com>
Date: Fri, 2 Sep 2016 15:36:02 -0400

Hey,

I was wondering what plans there are to allow Jersey clients to invoke
non-blocking IO without spawning a new thread? As far as I can tell, the
current design means that any async client calls will necessarily create
a new blocking thread - even when using a non-blocking client adapter
like the GrizzlyConnector or NettyConnector.

Thanks,
Grenville Wilson