getRXZeroCopy [virtual] | Return whether receive-side zero-copy is enabled. |
getZeroCopy [virtual] | Return whether zero-copy writes are enabled. |
setRXZeroCopy [virtual] | Enable or disable receive-side zero-copy using the given parameters. |
setZeroCopy [virtual] | Enable or disable zero-copy writes. |
setZeroCopyEnableFunc [virtual] | Set the predicate deciding when zero-copy writes are used. |
setZeroCopyEnableThreshold [virtual] | Set the minimum write size, in bytes, for using zero-copy writes. |
write [virtual] | If you supply a non-null WriteCallback, exactly one of writeSuccess() or writeErr() will be invoked when the write completes. If you supply the same WriteCallback object for multiple write() calls, it will be invoked exactly once per call. The only way to cancel outstanding write requests is to close the socket (e.g., with closeNow() or shutdownWriteNow()). When closing the socket this way, writeErr() will still be invoked once for each outstanding write operation. |
writeChain [virtual] | If you supply a non-null WriteCallback, exactly one of writeSuccess() or writeErr() will be invoked when the write completes. If you supply the same WriteCallback object for multiple write() calls, it will be invoked exactly once per call. The only way to cancel outstanding write requests is to close the socket (e.g., with closeNow() or shutdownWriteNow()). When closing the socket this way, writeErr() will still be invoked once for each outstanding write operation. |
writev [virtual] | If you supply a non-null WriteCallback, exactly one of writeSuccess() or writeErr() will be invoked when the write completes. If you supply the same WriteCallback object for multiple write() calls, it will be invoked exactly once per call. The only way to cancel outstanding write requests is to close the socket (e.g., with closeNow() or shutdownWriteNow()). When closing the socket this way, writeErr() will still be invoked once for each outstanding write operation. |