[
https://issues.apache.org/jira/browse/HTTPCLIENT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-427:
-----------------------------------------
Attachment: HTTPCLIENT-427-immutable-cachenentry.patch
Dave, Joe
I could not fully complete the changes that I had in mind. So far I managed to
have made all variables in the CacheEntry class final which helps a great deal
to ensure thread safety of the class, but I was unable to make it truly
immutable. Variant URIs can still be mutated by multiple threads leading to a
race condition. I have also failed miserably trying to wrap my head around
EasyMock which turned out to be far from easy. One of the test cases still
fails after my changes and I was not able to fix it nor to fully understand why
it is failing in the first place. I think it is better if you take over from
here and incorporate the patch (attached) into your change set.
Cheers
Oleg
> 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-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]
