[
https://issues.apache.org/jira/browse/HTTPCLIENT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865107#action_12865107
]
Sebb commented on HTTPCLIENT-427:
---------------------------------
@Joe:
>From the Javadoc for java.util.concurrent.atomic:
# get has the memory effects of reading a volatile variable.
# set has the memory effects of writing (assigning) a volatile variable.
The way I read that, there is no need to use volatile.
If there were, then AtomicLong would not be thread-safe.
I already changed CacheInvalidator to @ThreadSafe rather than @Immutable.
> 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-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]
