-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b11
Background in JDK-8260486, and discussion in https://mail.openjdk.java.net/pipermail/nio-dev/2021-January/008094.html
The proposal is to add a note to the transferFrom API docs to make it clearer a returning value of 0, meaning no bytes available, is ambiguous when the source channel is configured non-blocking. It could mean the source channel is at EOF or could mean that there are just no bytes available without blocking.
The proposal is to add a note to the transferFrom API docs to make it clearer a returning value of 0, meaning no bytes available, is ambiguous when the source channel is configured non-blocking. It could mean the source channel is at EOF or could mean that there are just no bytes available without blocking.
- csr for
-
JDK-8261135 (fc) Clarify FileChannel.transferFrom to better describe "no bytes available" case
-
- Closed
-
- relates to
-
-
- Closed
-
