Uses of Class
io.netty.util.concurrent.MultithreadEventExecutorGroup
Packages that use MultithreadEventExecutorGroup
Package
Description
The core channel API which is asynchronous and event-driven abstraction of
various transports such as a
NIO Channel.
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).
Utility classes for concurrent / async tasks.
-
Uses of MultithreadEventExecutorGroup in io.netty.channel
Subclasses of MultithreadEventExecutorGroup in io.netty.channelModifier and TypeClassDescriptionclass
MultithreadEventLoopGroup
which must be used for the local transport.class
Abstract base class forEventLoopGroup
implementations that handles their tasks with multiple threads at the same time. -
Uses of MultithreadEventExecutorGroup in io.netty.channel.epoll
Subclasses of MultithreadEventExecutorGroup in io.netty.channel.epoll -
Uses of MultithreadEventExecutorGroup in io.netty.channel.kqueue
Subclasses of MultithreadEventExecutorGroup in io.netty.channel.kqueue -
Uses of MultithreadEventExecutorGroup in io.netty.channel.local
Subclasses of MultithreadEventExecutorGroup in io.netty.channel.local -
Uses of MultithreadEventExecutorGroup in io.netty.channel.nio
Subclasses of MultithreadEventExecutorGroup in io.netty.channel.nioModifier and TypeClassDescriptionclass
-
Uses of MultithreadEventExecutorGroup in io.netty.util.concurrent
Subclasses of MultithreadEventExecutorGroup in io.netty.util.concurrentModifier and TypeClassDescriptionclass
Default implementation ofMultithreadEventExecutorGroup
which will useDefaultEventExecutor
instances to handle the tasks.
DefaultEventLoopGroup
instead.