JDK-4917674 : Need to update the ResponseCacheHandler API based on impl. experience
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 5.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-09-05
  • Updated: 2017-05-16
  • Resolved: 2003-09-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
5.0 tigerFixed
Related Reports
Relates :  
Relates :  
Based on our implementation experience, we feel that the ResponseCacheHandler API needs some adjustments in order to render it more effective. 

First, the current API would lead to caching the response body in the protocol handler upon receiving the response, doing so would have performance problems because the protocol handler has to do extra work before returning the response body to the caller, rather, the caching of response body is better driven by application reading the data and/or keep-alive cache trying to clean up the pipe.

Secondly, one additional parameter is added to ResponseCacheHandler.get() and ResponseCacheHandler.put() to align them more closely to the RFC specification.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b22

EVALUATION Will do before Tiger beta. ###@###.### 2003-09-04