hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Leigh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HTTPASYNC-45) CachingHttpAsyncClient Always Returns Backend's Future
Date Wed, 12 Jun 2013 19:46:20 GMT

     [ https://issues.apache.org/jira/browse/HTTPASYNC-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

James Leigh updated HTTPASYNC-45:

    Attachment: HTTPASYNC-45.patch

This patch creates FutureHttpResponse that wraps the backend's Future and allows CachingHttpAsyncClient
to override the response and failure exception.

> CachingHttpAsyncClient Always Returns Backend's Future
> ------------------------------------------------------
>                 Key: HTTPASYNC-45
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-45
>             Project: HttpComponents HttpAsyncClient
>          Issue Type: Bug
>    Affects Versions: 4.0-beta4
>            Reporter: James Leigh
>              Labels: patch
>             Fix For: 4.0-beta5
>         Attachments: HTTPASYNC-45.patch
> CachingHttpAsyncClient#execute methods always return the Future<HttpResponse> object
from the backend HttpAsyncClient. Calling Future#get() returns the backend HttpResponse (such
as 304) instead of the response in the cache.
> CachingHttpAsyncClient should create and use its own Future object that overrides the
Future#get() to return the HttpResponse in the cache.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

View raw message