[
https://issues.apache.org/jira/browse/HTTPCLIENT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865162#action_12865162
]
Joe Campbell commented on HTTPCLIENT-427:
-----------------------------------------
@Sam:
RE #1) Thank you for the more in depth explanation of volatile keywords use in
this case. This clarified the use of the keyword for me quite a bit and has
made my understanding of what that keyword 'really' does in code more precise.
RE #2) I think Jon covered that explanation. I think all here (that have
worked on the Caching client) agree that we would like to head down the path
that Oleg suggested - but we don't want that work to gate getting the 'working
foundation' of this code checked in and released. We are happy to continue to
work with the group to make suggested changes to improve and strengthen this
code base contribution.
Thanks,
Joe
> 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
> Fix For: 4.1 Alpha2
>
> Attachments: caching_client.zip,
> HTTPCLIENT-427-Immutable-CacheEntry2.patch,
> HTTPCLIENT-427-immutable-cachenentry.patch,
> HTTPCLIENT-427-rfc2616-sec13-tests.patch, httpclient-cache.zip
>
>
> 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]
