hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1493) Conditional stale connection checking
Date Thu, 05 Jun 2014 11:49:01 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018706#comment-14018706
] 

Oleg Kalnichevski commented on HTTPCLIENT-1493:
-----------------------------------------------

bq. What about my idea of implementing a check every N requests?

A better place for this kind of logic would be {{ConnectionReuseStrategy}} because one should
want to close the connection after a certain number of requests / bytes transferred upon _release_
rather than _lease_. We can this check to the connection pool if you like  but I would consider
it misplaced.

Oleg

> Conditional stale connection checking
> -------------------------------------
>
>                 Key: HTTPCLIENT-1493
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1493
>             Project: HttpComponents HttpClient
>          Issue Type: New Feature
>            Reporter: Sebb
>             Fix For: 4.4 Final
>
>
> Stale connection checking is expensive. At present if it is enabled, it is performed
for every connection. This is quite expensive and generates additional requests.
> One reason for a server to drop a connection is when the connection has been idle for
a while. Some servers send Keep-Alive headers to inform the client of this; if they don't,
then the client will see an unexpected disconnection. Stale connection checking avoids this
problem, but at the cost of additional requests. When a connection is not busy, this is acceptable,
but for a busy connection the checks are mostly unnecessary.
> Another reason for dropping a connection is after it has been reused many times. The
server should send a connection close as part of the final response, but if it does not, a
stale check would help.
> For these reasons, it would be useful to be able to implement conditional stale connection
checking, based on connection idle time and/or connection reuse count. These conditions should
be optionally selectable.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message