I see. There seems to be a pull request open to add support for
non-blocking calls when using a non-blocking connector
<
https://github.com/jersey/jersey/pull/206>. Is there anything I could
do to get it into a mergeable state? It seems a shame to have connectors
for Grizzly and Netty NIO clients, but no ability to actually engage in NIO.
On 09/07/2016 08:18 AM, Pavel Bucek wrote:
> 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
>>
>