Uses of Interface
io.netty.channel.ChannelOutboundInvoker

Packages that use ChannelOutboundInvoker
Package
Description
The helper classes with fluent API which enable an easy implementation of typical client side and server side channel initialization.
The core channel API which is asynchronous and event-driven abstraction of various transports such as a NIO Channel.
A virtual Channel that helps wrapping a series of handlers to unit test the handlers or use them in non-I/O context.
Optimized transport for linux which uses EPOLL Edge-Triggered Mode for maximal performance.
BSD specific transport.
A virtual transport that enables the communication between the two parties in the same virtual machine.
NIO-based channel API implementation - recommended for a large number of connections (>= 1000).
Old blocking I/O based channel API implementation - recommended for a small number of connections (< 1000).
Abstract TCP and UDP socket interfaces which extend the core channel API.
NIO-based socket channel API implementation - recommended for a large number of connections (>= 1000).
Old blocking I/O based socket channel API implementation - recommended for a small number of connections (< 1000).
Unix specific transport.
Encoder, decoder, handshakers and their related message types for Web Socket data frames.
Handlers for sending and receiving HTTP/2 frames.