[
https://issues.apache.org/jira/browse/HTTPCLIENT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851047#action_12851047
]
Jonathan Moore commented on HTTPCLIENT-427:
-------------------------------------------
Hi folks,
We had a group of engineers work on a CachingHttpClient as a "lab week" project
last week, following (as it turns out) the same decorator pattern Oleg
outlined. We've also developed a pluggable cache storage interface and have
in-memory (basically a LRU HashMap), ehcache, and memcache backends. We're not
quite standards-compliant yet, but hopefully will be soon.
Currently this builds as a separate JAR with all the classes under
org.apache.http.client.cache as a new package (the adapters for the ehcache and
memcache backends are also separate JARs so you can just include the
dependencies you need).
We'd like to contribute this back to the community; are there any particulars
about the best way to do this?
Thanks,
Jon Moore
Comcast Interactive Media
> Implement a cache to perform real request only when needed
> ----------------------------------------------------------
>
> Key: HTTPCLIENT-427
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-427
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Environment: Operating System: Linux
> Platform: PC
> Reporter: Marc Guillemot
> Priority: Minor
> Fix For: Future
>
>
> Browsers may cache received content according to the values of different
> response headers. It would be great if HttpClient could do the same.
--
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-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
