users@jersey.java.net

[Jersey] Re: Non-blocking client without Jersey's thread pool

From: Pavel Bucek <pavel.bucek_at_oracle.com>
Date: Wed, 7 Sep 2016 14:18:17 +0200

Hi Grenville,

async is not non-blocking .. but I guess you know that.

Yes, there are plans to do NIO for JAX-RS 2.1 (and consequently for
Jersey, since it is the reference implementation).

Unfortunately, there is no ETA yet.

Regards,
Pavel


On 02/09/16 21:36, Grenville Wilson wrote:
> 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
>