Thanks for your thoughts, on multiple transports. selector pools. One of
the reasons I was asking these questions is because i'm seeing timeout
errors when testing with this proxy scenario which seem to be dependant on
the ratio of inbound/outbound selector threads, but I need to do some
further testing before confirming this is a real issue..
is a connection in the connection pool - AHC will obtain it in the same
> thread, but if there is no connection - then yes it will probably obtain it
> asynchronously.
>
> My mistake, I mis-read this code.
> - 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.
Dan