[
https://issues.apache.org/jira/browse/HTTPASYNC-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682273#comment-13682273
]
Oleg Kalnichevski commented on HTTPASYNC-44:
--------------------------------------------
@James
All responses returned by the current backend are non-streaming (in-memory) and
do not to be consumed.
@Jon
There is also a LOT of work that also needs to be done inside HttpAsyncClient
in order to enable dynamic wiring of the execution pipeline similar to that we
now have in HttpClient 4.3. Unfortunately I just do not have time for that and
possibly never will.
Oleg
> CachingHttpAsyncClient Has Gotten Out Of Sync With CachingExec
> --------------------------------------------------------------
>
> Key: HTTPASYNC-44
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-44
> Project: HttpComponents HttpAsyncClient
> Issue Type: Bug
> Affects Versions: 4.0-beta4
> Reporter: James Leigh
> Labels: patch
> Fix For: 4.0-beta5
>
> Attachments: consumeQuietly.patch, HTTPASYNC-44.patch
>
>
> Many fixes for CachingExec have not bee applied to CachingHttpAsyncClient,
> which copied much of it's code from CachingExec.
--
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: [email protected]
For additional commands, e-mail: [email protected]
