-
Enhancement
-
Resolution: Fixed
-
P3
-
14
-
b10
This issue proposes to deprecate, and eventually remove, the API points
for statically configuring a system-wide factory for the socket types in
the java.net package. Specifically, the following:
* Methods:
1) static void ServerSocket.setSocketFactory(SocketImplFactory fac)
2) static void Socket.setSocketImplFactory(SocketImplFactory fac)
3) static void DatagramSocket.setDatagramSocketImplFactory(DatagramSocketImplFactory fac)
* Types
a) java.net SocketImplFactory
b) java.net DatagramSocketImplFactory
The java.net SocketImplFactory and DatagramSocketImplFactory types can
be deprecated too, since their only use relates to the above factory
setter methods.
The CSR forJDK-8220494 contains some verbiage about the potential
issues that setting factories can have, and alludes to their possible
future removal.
for statically configuring a system-wide factory for the socket types in
the java.net package. Specifically, the following:
* Methods:
1) static void ServerSocket.setSocketFactory(SocketImplFactory fac)
2) static void Socket.setSocketImplFactory(SocketImplFactory fac)
3) static void DatagramSocket.setDatagramSocketImplFactory(DatagramSocketImplFactory fac)
* Types
a) java.net SocketImplFactory
b) java.net DatagramSocketImplFactory
The java.net SocketImplFactory and DatagramSocketImplFactory types can
be deprecated too, since their only use relates to the above factory
setter methods.
The CSR for
issues that setting factories can have, and alludes to their possible
future removal.
- csr for
-
JDK-8261228 Deprecate the socket impl factory mechanism
-
- Closed
-
- is blocked by
-
-
- Resolved
-
- relates to
-
JDK-8261521 Release Note: Deprecate the Socket Implementation Factory Mechanism
-
- Closed
-
-
JDK-8338940 Cannot Socket Options for HTTP Client After Recent Deprecation/Removal
-
- Closed
-
-
-
- Open
-
-
JDK-8235674 JEP 373: Reimplement the Legacy DatagramSocket API
-
- Closed
-
(1 relates to, 2 links to)