geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor" <jga...@gmail.com>
Subject Re: Is there a problem with AsyncHttpClient connection reuse?
Date Mon, 14 Jan 2008 21:09:07 GMT
On 1/14/08, Sangjin Lee <sjlee0@gmail.com> wrote:
> It's a good point...  Currently the session cache is global, and all
> AsyncHttpClient instances are forced to share it.  The main thing that
> concerns me is that as a result the connections will retain all the socket
> properties that came from the AsyncHttpClient instance that opened the
> connection.  This might not be intuitive to say the least.  For example, one
> AsyncHttpClient instance opens a connection with TCP delay disabled, and
> then another instance (this time with TCP delay enabled) comes along and
> picks up this connection for reuse.  Contrary to what it expects, it would
> get a connection with TCP delay disabled.

Right and this might be a bigger issue for SSL connections where you
might need to distinguish between cached connections based on the
client certs, CA certs, or enabled cipher suites (but I'm not sure if
these options can be set on the AsyncHttpClient).

Jarek

Mime
View raw message