Name: mc57594 Date: 02/28/97
In attempting to implement the REXEC protocols, I need the ability to close the output side of a socket, while continuing to use the input side of the socket. In other words, closing the output side indicates to the rexec-ed process that EOF has been reached and input data is complete. However, when I close the output side, the input side of the socket is no longer functional.
I need to be able to close one side of the socket, indicating EOF, while continuing to read input from the socket. If this is not clear, please consult documentation on the REXEC protocol.
This is the third time I have reported this bug!
company - ICE Engineering, Inc. , email - ###@###.###
======================================================================
[ from bugid 4118429, db@eng, 10 March 1998 ]:
The RFE is that since most "normal" sockets support the ability to
close one side of the socket, but not the other (i.e. "normal" being
"what you can do with the Berkeley C sockets API), so should Java
sockets offer this feature.
Lack of this functionality prevents certain kinds of application
protocols from working. Specifically, ones which work to ensure
delivery of all application data before terminating connections.
In attempting to implement the REXEC protocols, I need the ability to close the output side of a socket, while continuing to use the input side of the socket. In other words, closing the output side indicates to the rexec-ed process that EOF has been reached and input data is complete. However, when I close the output side, the input side of the socket is no longer functional.
I need to be able to close one side of the socket, indicating EOF, while continuing to read input from the socket. If this is not clear, please consult documentation on the REXEC protocol.
This is the third time I have reported this bug!
company - ICE Engineering, Inc. , email - ###@###.###
======================================================================
[ from bugid 4118429, db@eng, 10 March 1998 ]:
The RFE is that since most "normal" sockets support the ability to
close one side of the socket, but not the other (i.e. "normal" being
"what you can do with the Berkeley C sockets API), so should Java
sockets offer this feature.
Lack of this functionality prevents certain kinds of application
protocols from working. Specifically, ones which work to ensure
delivery of all application data before terminating connections.
- duplicates
-
JDK-4091706 TCP socket input and output streams fail to observe TCP half-close semantics
-
- Closed
-
-
JDK-4118429 Sockets can't be "half open"
-
- Closed
-
-
JDK-4216431 Wanted: equivalent of C shutdown(2) call on socket
-
- Closed
-
-
JDK-4250179 RFE: There should be a way to partially shutdown TCP connections
-
- Closed
-