You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Jon Moore (JIRA)" <ji...@apache.org> on 2013/06/13 15:56:20 UTC
[jira] [Commented] (HTTPASYNC-44) CachingHttpAsyncClient Has Gotten
Out Of Sync With CachingExec
[ https://issues.apache.org/jira/browse/HTTPASYNC-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682256#comment-13682256 ]
Jon Moore commented on HTTPASYNC-44:
------------------------------------
I also think there's value to having a cache on the async client, but the current approach is really a stopgap measure. I believe the right approach here, ultimately, is to do some refactoring on the synchronous caching subsystem, as James suggests, so that most of it can be directly reused by an asynchronous version over here. It's not entirely trivial, as the logical caching workflow is somewhat involved, between having cache hits, cache misses, revalidations (sync and async), etc.
I'll open a new issue to track this improvement.
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org