[
https://issues.apache.org/jira/browse/HTTPCLIENT-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304457#comment-16304457
]
ASF subversion and git services commented on HTTPCLIENT-1824:
-------------------------------------------------------------
Commit 749b02ac0377edf87b41122aea0a8ae692dbdb1d in httpcomponents-client's
branch refs/heads/master from [~olegk]
[ https://git-wip-us.apache.org/repos/asf?p=httpcomponents-client.git;h=749b02a
]
HTTPCLIENT-1824: asynchronous HTTP cache executor to use asynchronous HTTP
cache APIs; changed algorithm of the backend response freshness check (both
classic and async cache implementations)
> Async caching module is not async for cache I/O and does not share enough
> implementation with synchronous client cache
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1824
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1824
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Reporter: Jon Moore
> Labels: cache
> Fix For: 5.0
>
>
> As noted in HTTPASYNC-44, the caching module for the asynchronous client may
> do synchronous I/O when talking to cache storage; this isn't entirely clean
> and may violate client assumptions. In addition, there may need to be some
> refactoring of the synchronous client caching module so that more of the
> logic can be shared with the asynchronous stack.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]