[
https://issues.apache.org/jira/browse/HTTPCLIENT-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196041#comment-16196041
]
Oleg Kalnichevski commented on HTTPCLIENT-1874:
-----------------------------------------------
HttpClient already provides quite a sophisticated back-off mechanism. Please
have a look those classes below and if possible please leverage APIs that are
already in place
https://github.com/apache/httpcomponents-client/blob/4.6.x/httpclient/src/main/java/org/apache/http/impl/execchain/BackoffStrategyExec.java
https://github.com/apache/httpcomponents-client/blob/4.6.x/httpclient/src/main/java/org/apache/http/impl/client/AIMDBackoffManager.java
https://github.com/apache/httpcomponents-client/blob/4.6.x/httpclient/src/main/java/org/apache/http/impl/client/DefaultBackoffStrategy.java
The problem is that the original contributor never got around to documenting
the APIs. See HTTPCLIENT-1101
Oleg
> Exponential back-off retry mechanism
> ------------------------------------
>
> Key: HTTPCLIENT-1874
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1874
> Project: HttpComponents HttpClient
> Issue Type: New Feature
> Reporter: Ioannis Sermetziadis
>
> I believe it would be useful to have an Exponential Back-off algorithm
> implementation, as an HttpRequestRetryHandler or under a new interface, named
> HttpRequestRetryPolicy.
> The implementation could provide both synchronous (similar to the existing
> retry mechanism) and asynchronous retries, using a provided
> ExecutorService/ScheduledExecutorService.
> Any feedback would be much appreciated. If you agree with the value of such a
> feature, I could proceed to the implementation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
