Among other things, the following should be considered and evaluated:
1. Drop the support for DatagramSocketImpl implementations that are compiled with JDK 1.3 or older.
2. Drop the filtering when the DatagramSocket is connected. Instead, DatagramSocketImpl.connect should flush the read queue after the address association is setup.
3. Change DatagramSocket.recieve so that the security manager case when not connected always receives into a temporary buffer. This will eliminate the need to peek ahead.
Other preparatory work that could make it easier to provide an alternative implementation should also be considered.
- is blocked by
-
JDK-8233319 Deprecate MulticastSocket methods that operate on java.net.InetAddress
-
- Resolved
-
-
JDK-8235141 Specify the required standard socket options for the socket types in the java.net package
-
- Resolved
-
-
JDK-8231259 (dc) DatagramChannel::disconnect re-binds socket to the wildcard address (macOS)
-
- Resolved
-
-
JDK-8231260 (dc) DatagramChannel::disconnect changes the port of the local address to 0 (lnx)
-
- Resolved
-
-
JDK-8231570 (dc) Clarify implicit bind behavior of DatagramChannel
-
- Resolved
-
-
JDK-8233191 MulticastSocket joinGroup/leaveGroup do not specify their behavior when the outgoing interface has not been set
-
- Resolved
-
-
JDK-8233860 java/net/SocketOption/AfterClose.java test incorrectly handles IP_MULTICAST_IF
-
- Resolved
-
-
JDK-8234083 DatagramSocket should report SO_BROADCAST as a supported option
-
- Resolved
-
-
JDK-8235783 DatagramSocket::connect and DatagramSocket::disconnect should allow an implementation to throw UncheckedIOException
-
- Resolved
-
-
JDK-8236105 Behaviors of DatagramSocket/DatagramChannel::socket send methods are not always consistent
-
- Resolved
-
-
JDK-8230946 Clarify security manager behaviour of a connected DatagramSocket and DatagramChannel
-
- Closed
-
-
JDK-8146298 (dc spec) connect and disconnect methods should specify that they may block
-
- Closed
-
-
JDK-8222829 DatagramSocket.setSoTimeout does not specify IAE when timeout is negative
-
- Closed
-
-
JDK-8232673 (dc) DatagramChannel socket adaptor issues
-
- Closed
-
-
JDK-8233141 DatagramSocket.send doesn't specify exception thrown when no target address
-
- Closed
-
-
JDK-8233296 MulticastSocket getOption/setOption inverts the value of IP_MULTICAST_LOOP
-
- Closed
-
-
JDK-8233307 MulticastSocket getOption(IP_MULTICAST_IF) returns interface when not set
-
- Closed
-
-
JDK-8234103 DatagramSocketImpl::socket is not needed
-
- Closed
-
-
JDK-8233435 (dc) DatagramChannel should allow IPv6 socket join IPv4 multicast groups (macOS, win)
-
- Resolved
-
-
JDK-8234148 DatagramSocket.setOption/getOption/supportedOption should support multicast options
-
- Resolved
-
-
JDK-8236184 (dc) IP_MULTICAST_* and IP_TOS socket options not effective
-
- Resolved
-
-
JDK-8236246 SelectorProvider support for creating a DatagramChannel that is not interruptible
-
- Resolved
-
-
JDK-8236925 (dc) Upgrade DatagramChannel socket adaptor to extend MulticastSocket
-
- Resolved
-
- relates to
-
JDK-8234103 DatagramSocketImpl::socket is not needed
-
- Closed
-
-
JDK-8235674 JEP 373: Reimplement the Legacy DatagramSocket API
-
- Closed
-
-
JDK-8243488 Add tests for set/get SendBufferSize and getReceiveBufferSize in DatagramSocket
-
- Resolved
-
-
JDK-7141822 java/nio/channels/DatagramChannel/ChangingAddress.java failing on OS X
-
- Closed
-
-
JDK-7143960 java/net/DatagramSocket/SendDatagramToBadAddress.java is failing on Mac OS X
-
- Closed
-
-
JDK-8239355 (dc) Initial value of SO_SNDBUF should allow sending large datagrams (macOS)
-
- Resolved
-