>> - Even if the same selector pool is configured for inbound and
>> outbound, during response processing then Grizzly will still do a
>> thread handover before sending response to client because of the
>> use of AsyncQueueIO. This right?
> Not sure I understand this, IMO there won't be any extra thread
> handover involved.
>
>
> I was referring to the AsyncWriteQueue. Currently I
> have 'optimizedForMultiplexing' set true which I thought I'd seen
> previsouly disabled the direct writing as you described further on in
> your email. Pherhaps I should try without this flag though.
Right, optimizedForMultiplexing is useful, when you concurrently write
packets to the connection, which is not the case with HTTP, unless it's
HTTP 2.0 :)
Thanks.
WBR,
Alexey.