[
https://issues.apache.org/jira/browse/HTTPCLIENT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835277#action_12835277
]
Avlesh Singh commented on HTTPCLIENT-427:
-----------------------------------------
Thanks Oleg, these would be good for me to get started.
For your #3, shouldn't caching be tightly coupled with HttpClient rather than
being implemented as a decorator? More so, because, caching can only be
implemented if the response headers direct an HttpClient instance to do so.
Having said this, I definitely agree to the fact that actual cache should be an
API implementation thereby giving users the flexibility to use a custom cache.
I'll come up with a basic cache API definition and share shortly.
> 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: [email protected]
For additional commands, e-mail: [email protected]
