You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2010/08/18 21:45:19 UTC
[jira] Resolved: (HTTPCLIENT-979) cache entry resource management
should be extracted from CachingHttpClient
[ https://issues.apache.org/jira/browse/HTTPCLIENT-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-979.
------------------------------------------
Fix Version/s: 4.1 Alpha3
Resolution: Fixed
Patch checked in. Many thanks for contributing it, Jon.
How certain are you about stability of HttpCache interface, though? Once 4.1 beta1 is released we will no longer be able to change it. Would it be worthwhile to consider making an abstract class out of it and making those methods that are unlikely to very in different implementations non-abstract?
Oleg
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org