[
https://issues.apache.org/jira/browse/HTTPCLIENT-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863786#action_12863786
]
Joe Campbell commented on HTTPCLIENT-427:
-----------------------------------------
Yes - they can be made private and final - as they are never meant to change.
In fact, I added the @Immutable annotation to the class (similar to other
classes assumed to have been modified by Oleg). OptionsHttp11Response's
purpose is to serve as the response container for a request OPTIONS query with
maxforwards set to 0 (essentially a loopback to indicate all the various things
that the cache will support).
This change will be included in a patch from us when Oleg is complete with
making CacheEntry immutable as well. We are trying not to collide changes by
pausing to wait for Oleg's changes on the tree and then supplying a patch for
some of the other minor changes requested based on that.
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-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]
