Package io.netty.channel
package io.netty.channel
The core channel API which is asynchronous and event-driven abstraction of
various transports such as a
NIO Channel.
-
ClassDescriptionA skeletal
Channelimplementation.Skeletal implementation ofEventLoop.Skeletal implementation ofEventLoopGroup.A skeletal server-sideChannelimplementation.TheRecvByteBufAllocatorthat automatically increases and decreases the predicted buffer size on feed back.AddressedEnvelope<M, A extends SocketAddress>A message that wraps another message with a sender address and a recipient address.A nexus to a network socket or a component which is capable of I/O operations such as read, write, connect, and bind.Unsafe operations that should never be called from user-code.A set of configuration properties of aChannel.ChannelHandlerimplementation which represents a combination out of aChannelInboundHandlerand theChannelOutboundHandler.ARuntimeExceptionwhich is thrown when an I/O operation fails.ChannelFactory<T extends Channel>Creates a newChannel.This implementation allows to registerChannelFutureinstances which will get notified once some amount of data was written and so a checkpoint was reached.The result of an asynchronousChannelI/O operation.Listens to the result of aChannelFuture.Handles an I/O event or intercepts an I/O operation, and forwards it to its next handler in itsChannelPipeline.Indicates that the same instance of the annotatedChannelHandlercan be added to one or moreChannelPipelines multiple times without a race condition.Skeleton implementation of aChannelHandler.Enables aChannelHandlerto interact with itsChannelPipelineand other handlers.Represents the globally unique identifier of aChannel.ChannelHandlerwhich adds callbacks for state changes.Abstract base class forChannelInboundHandlerimplementations which provide implementations of all of their methods.ChannelInitializer<C extends Channel>A specialChannelInboundHandlerwhich offers an easy way to initialize aChannelonce it was registered to itsEventLoop.Represents the properties of aChannelimplementation.AChannelOptionallows to configure aChannelConfigin a type-safe way.(Transport implementors only) an internal data structure used byAbstractChannelto store its pending outbound write requests.ChannelHandlerwhich will get notified for IO-outbound-operations.Skeleton implementation of aChannelOutboundHandler.A list ofChannelHandlers which handles or intercepts inbound events and outbound operations of aChannel.AChannelExceptionwhich is thrown when aChannelPipelinefailed to execute an operation.An specialChannelFuturewhich is used to indicate theFileRegiontransfer progressAnEventListenerlistener which will be called once the sending task associated with future is being transferred.SpecialChannelPromisewhich will be notified once the associated bytes is transferring.SpecialChannelFuturewhich is writable.Deprecated.UsePromiseCombinerClass which is used to consolidate multiple channel futures into one, by listening to the individual futures and producing an aggregated result (success/failure) when all futures have completed.Deprecated.usePromiseNotifier.A FIFO queue of bytes where producers add bytes by repeatedly addingByteBufand consumers take bytes in arbitrary lengths.ConnectExceptionwhich will be thrown if a connection could not be established because of a connection timeout.DefaultAddressedEnvelope<M, A extends SocketAddress>The defaultAddressedEnvelopeimplementation.The defaultChannelConfigimplementation.The defaultChannelIdimplementation.The defaultChannelPipelineimplementation.The defaultChannelProgressivePromiseimplementation.The defaultChannelPromiseimplementation.Deprecated.TheRecvByteBufAllocatorthat yields a buffer size prediction based upon decrementing the value from the max bytes per read.Default implementation ofMaxMessagesRecvByteBufAllocatorwhich respectsChannelConfig.isAutoRead()and also prevents overflow.DefaultMessageSizeEstimatorimplementation which supports the estimation of the size ofByteBuf,ByteBufHolderandFileRegion.Factory which uses the default select strategy.Will handle all the I/O operations for aChannelonce registered.SpecialChannelExceptionwhich will be thrown byEventLoopandEventLoopGroupimplementations when an error occurs.SpecialEventExecutorGroupwhich allows registeringChannels that get processed for later selection during the event loop.Deprecated.Not used anymore by newIoEventLoopGroupandIoEventLoopimplementationsA region of a file that is sent via aChannelwhich supports zero-copy file transfer.TheRecvByteBufAllocatorthat always yields the same buffer size prediction.EventLoopGroupforIoEventLoops.A handle that can be registered to anIoHandler.Handles IO dispatching for anThreadAwareExecutor.The context for anIoHandlerthat is run by anThreadAwareExecutor.Factory forIoHandlerinstances.An IO op that can be submitted to anIoRegistrationviaIoRegistration.submit(IoOps). // * These submittedIoOpswill result inIoEvents on the relatedIoHandle.A registration for IO.IoEventLoopimplementation that is owned by the user and so needs to be driven by the user manually with the givenThread.RecvByteBufAllocatorthat limits a read operation based upon a maximum value per individual read and a maximum amount when a read operation is attempted by the event loop.RecvByteBufAllocatorthat limits the number of read operations that will be attempted when a read operation is attempted by the event loop.Responsible to estimate the size of a message.Abstract base class forEventLoopGroupimplementations that handles their tasks with multiple threads at the same time.IoEventLoopGroupimplementation that will handle its tasks with multiple threads.A queue of write operations which are pending for later execution.Wraps anotherByteBufAllocatorand use heapbuffers everywhere except when a direct buffer is explicit requested.Allocates a new receive buffer whose capacity is probably large enough to read all inbound data and small enough not to waste its space.ARecvByteBufAllocator.Handlewhich delegates all call to some otherRecvByteBufAllocator.Handle.Deprecated.ReflectiveChannelFactory<T extends Channel>AChannelFactorythat instantiates a newChannelby invoking its default constructor reflectively.Select strategy interface.Factory that creates a newSelectStrategyevery time.MaxMessagesRecvByteBufAllocatorimplementation which should be used forServerChannels.ChannelInboundHandlerAdapterwhich allows to explicit only handle a specific type of messages.ChannelInboundHandlerAdapterwhich allows to conveniently only handle a specific type of user events.Abstract base class forEventLoops that execute all its submitted tasks in a single thread.IoEventLoopimplementation that execute all its submitted tasks in a single thread using the providedIoHandler.Deprecated.this will be remove in the next-major release.Deprecated.this will be remove in the next-major release.WriteBufferWaterMark is used to set low water mark and high water mark for the write buffer.