[
https://issues.apache.org/jira/browse/HTTPCLIENT-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922124#action_12922124
]
Oleg Kalnichevski commented on HTTPCLIENT-1005:
-----------------------------------------------
> This probably consists of additional constructors on CachingHttpClient that
> take HttpCacheStorage in place of HttpCache
> (where the implementation just wraps those in a BasicHttpCache).
Yep. I added two new constructors that take a HttpCacheStorage and optionally a
ResourceFactory. This, at the very least, enables the users to customise the
way cache entries are persisted, which is pretty essential in my opinion
(consider this a request ;-)). As a small bonus we can keep Ehcache and
memcached related stuff in separate packages.
Oleg
> API surface of caching module can be reduced
> --------------------------------------------
>
> Key: HTTPCLIENT-1005
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1005
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Jonathan Moore
> Attachments: smaller-api.patch
>
>
> While the caching module can currently be considered functional and useful
> for folks as-is, there are several near-term enhancements planned that could
> change the exposed binary API of the caching module (although it is not yet
> clear whether they would or not). In an effort to allow the 4.1 GA release to
> go forward while hedging bets against future development, we should consider
> drastically reducing the exposed binary API of the caching module, and not
> exposing extension points until someone explicitly asks for them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
