Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

APIMethodsNotes
java.net.Socketconnect, read, write
java.net.ServerSocketaccept
java.net.DatagramSocket/MulticastSocketreceivesend does not block



java.nio.channels.SocketChannelconnect, read, writesocket adaptor connect, read, and write also okay
java.nio.channels.ServerSocketChannelacceptsocket adaptor accept also okay
java.nio.channels.DatagramChannelread, receive

socket adaptor receive also okay

write and send do not block

java.nio.channels.Pipe.SourceChannelread
java.nio.channels.Pipe.SinkChannelwrite
java.net.InetAddressgetByName, getAllByName, ..

These methods currently off load name/address resolution to a background thread pool where threads block in the underlying NSS/equivalent. An alternative name service implementation for InetAddress is being developed in the sandbox (aefimov-dns-client-branch) that will be virtual thread friendly.

...

The following blocking operations are not currently virtual thread friendly; these methods pin the carrier thread when the operation blocks.

This will be resolved when DatagramSocket's implementation is replaced. The foundation work for this replacement has done in the main line for JDK 14.
APIMethodsNotesjava.net.DatagramSocket/MulticastSocketreceive
java.nio.channels.SelectorselectSelection operations are specified to synchronize on the selector and the selected-key set. May not be a concern as code using fibers should not need to use non-blocking I/O and Selectors.