JDK-6819122 : DefaultProxySelector should lazily initialize the Pattern object and the NonProxyInfo objects
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 7
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2009-03-18
- Updated: 2010-04-02
- Resolved: 2009-04-11
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 Availability Release.
To download the current JDK release, click here.
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 Availability Release.
To download the current JDK release, click here.
| JDK 6 | JDK 7 |
|---|---|
6u14Fixed  |
7 b55Fixed |
Related Reports
|
Relates :
|
Description
DefaultProxySelector has a few static variables (e.g. ftpNonProxyInfo and httpNonProxyInfo and the Pattern object) that are not always needed at startup. We can defer its initialization until it's needed.
Comments
|