Uses of Interface
io.netty.util.concurrent.Future

Packages that use Future
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.
A channel registry which helps a user maintain the list of open Channels and perform bulk operations on them.
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).
Implementations and API for Channel pools.
Handlers for sending and receiving HTTP/2 frames.
Adds support for client connections via proxy protocols such as SOCKS and HTTP CONNECT tunneling
SSL · TLS implementation based on SSLEngine
Adds support for read and write timeout and idle connection notification using a Timer.
Resolves an arbitrary string that represents the name of an endpoint into an address.
An alternative to Java's built-in domain name lookup mechanism that resolves a domain name asynchronously, which supports the queries of an arbitrary DNS record type as well.
Utility classes used across multiple packages.
Utility classes for concurrent / async tasks.