geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Genender (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3686) AsyncHttpClient does not reuse connection even if connections are persistent
Date Fri, 07 Dec 2007 18:41:43 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549510
] 

Jeff Genender commented on GERONIMO-3686:
-----------------------------------------

Cool stuff.  Yep...FIFO would be the way I would do the queues.  A ConcurrentLinkedQueue is
perfect for this.  For the container that holds these queues, a ConcurrentHashmap would be
great.

Instead of the sendRequest() checking the connection validation, why not make this a facet
of the checking out.  In fact this whole thing could be part of a connection manager/connection
cache that will return one if it exists (an is valid) or creates it if one doesn't.

The ideas look very sound and looks good to me.

> AsyncHttpClient does not reuse connection even if connections are persistent
> ----------------------------------------------------------------------------
>
>                 Key: GERONIMO-3686
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3686
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: AsyncHttpClient
>    Affects Versions: 1.x
>            Reporter: Sangjin Lee
>
> Each time AsyncHttpClient.sendRequest() is called, a new TCP connection is opened, even
though connections may be kept alive per HTTP spec.  If connections are kept open, they should
be reused for more requests.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message