ByteBuffer which has the same ByteOrder as the native order of the machine.InetSocketAddress to be able to easily pass all needed data from JNI without the need
to create more objects then needed.UnixChannel that supports communication via
UNIX domain datagram sockets.ChannelConfig for a DomainDatagramChannel.DomainDatagramChannel to communicate with the remote peer.data and recipient address.data, recipient address, and sender
address.DomainSocketAddress to be able to easily pass all needed data from JNI without the need
to create more objects then needed.UnixChannel that supports communication via
Unix Domain Socket.ChannelConfig for DomainSocketChannels.DomainSocketChannel.FileDescriptor that is used by this Channel.FileDescriptor implementation which allows to wrap an int and provide a
FileDescriptor for it.ByteBuffer.FileDescriptor for the given path.FileDescriptor for the given File.DomainSocketReadMode for the channel.StandardSocketOptions.SO_SNDBUF option.iovec struct in bytes.true if the DomainDatagramChannel is connected to the remote peer.true if the file descriptor is open.IovArray via IovArray.add(ByteBuf, int, int)
This will not impact the existing state of the IovArray, and only applies to subsequent calls to
IovArray.add(ByteBuf).IovArray.ByteBuffer.memoryAddress for the given offset.IovArray.DomainSocketReadMode for the channel.StandardSocketOptions.SO_SNDBUF option.netty-transport-native-unix is
supported.Channel that expose operations that are only present on UNIX like systems.true if the given socket and address combination should use IPv6 internally,
false otherwise.Copyright © 2008–2024 The Netty Project. All rights reserved.