[
https://issues.apache.org/jira/browse/HTTPCLIENT-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900025#action_12900025
]
Jonathan Moore commented on HTTPCLIENT-979:
-------------------------------------------
I think the easiest way to answer this will be to get the following cache
implementations sanity-checked:
1. your "store the bodies on the filesystem" cache
2. the memcached cache
3. the ehcache cache
The one other suspicion I have is that the HttpCache#cacheEntry method might
want to return an HttpResponse instead of an HttpCacheEntry. This would move
revalidation into the BasicHttpCache, leaving the CachingHttpClient very simple
indeed. I think let's get #1-#3 shorn up and then see where we are.
What is the target release date for 4.1-beta1?
> cache entry resource management should be extracted from CachingHttpClient
> --------------------------------------------------------------------------
>
> Key: HTTPCLIENT-979
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-979
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 4.1 Alpha2
> Reporter: Jonathan Moore
> Fix For: 4.1 Alpha3
>
> Attachments: separate-cache-and-storage.patch
>
>
> As we have built in support for stream-based management of cached response
> bodies, the CachingHttpClient class has its fingers in too many pies and is
> involved in resource management but not storage of the actual
> HttpCacheEntries.
> I have a patch forthcoming. :)
--
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]
