[
https://issues.apache.org/jira/browse/HTTPASYNC-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Leigh updated HTTPASYNC-44:
---------------------------------
Attachment: consumeQuietly.patch
Hi Oleg,
I think there is still value in having a caching client for the async API (even
if it blocks i/o when consuming potentially cached backend responses). I think
HttpAsyncClient could be cleaned up, but unless CachingExec is broken into
smaller files there will be more of copying of code still to come.
The patch used trace priority wherever CachingExec used trace priority, I
included those changes to keep the code similar.
The svn commit seems to be missing the EntityUtils.consumeQuietly calls when
rejecting 304 backend responses. I have included consumeQuietly.patch with
these.
James
> 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]
