You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2013/06/13 09:58:20 UTC

[jira] [Resolved] (HTTPASYNC-45) CachingHttpAsyncClient Always Returns Backend's Future

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

Oleg Kalnichevski resolved HTTPASYNC-45.
----------------------------------------

    Resolution: Fixed

Patch committed to SVN trunk. Please review.

Oleg
                
> 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