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

Oleg Kalnichevski commented on HTTPCORE-374:
--------------------------------------------

Patches committed to HttpClient and HttpAsyncClient trunks. Many thanks, 
Dmitry, for contributing them.

Oleg

> ConnPoolControl should provide list of known routes
> ---------------------------------------------------
>
>                 Key: HTTPCORE-374
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-374
>             Project: HttpComponents HttpCore
>          Issue Type: Improvement
>          Components: HttpCore, HttpCore NIO
>            Reporter: Dmitry Potapov
>            Priority: Trivial
>             Fix For: 4.4-alpha1
>
>         Attachments: 01-PoolingHttpClientConnectionManager-getRoutes.patch, 
> 01-PoolingNHttpClientConnectionManager-getRoutes.patch, 
> httpasyncclient-getRoutes.patch, httpasyncclient-getRoutes.patch, 
> httpclient-getRoutes.patch, httpclient-getRoutes.patch, 
> httpcore-getRoutes.patch, httpcore-getRoutes.patch
>
>
> Currently ConnPoolControl.getStats(HttpRoute) requires caller to store known 
> routes somewhere to get complete detailed connections stats, for example, 
> when checking for slow backends.
> My suggestion is to add Set<T> getRoutes(); function to ConnPoolControl which 
> will return snapshot of all routes served by this pool.
> With this function it will be able to get all routes stats, detect the weak 
> links among backends and report them.
> I understand, that this change will break compatibility and won't be shipped 
> with any 4.3.x version, but can we have this in 4.4?



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to