Package org.jboss.netty.channel

Interface ChannelSink

All Known Implementing Classes:

AbstractChannelSink, AbstractCodecEmbedder.EmbeddedChannelSink, AbstractNioChannelSink, AbstractOioChannelSink, DefaultChannelPipeline.DiscardingChannelSink, HttpTunnelingClientSocketPipelineSink, LocalClientChannelSink, LocalServerChannelSink, NioClientSocketPipelineSink, NioDatagramPipelineSink, NioServerSocketPipelineSink, OioClientSocketPipelineSink, OioDatagramPipelineSink, OioServerSocketPipelineSink

public interface ChannelSink

Receives and processes the terminal downstream ChannelEvents.

A ChannelSink is an internal component which is supposed to be implemented by a transport provider. Most users will not see this type in their code.

Method Summary

Modifier and Type	Method	Description
void	eventSunk(ChannelPipeline pipeline, ChannelEvent e)	Invoked by ChannelPipeline when a downstream ChannelEvent has reached its terminal (the head of the pipeline).
void	exceptionCaught(ChannelPipeline pipeline, ChannelEvent e, ChannelPipelineException cause)	Invoked by ChannelPipeline when an exception was raised while one of its ChannelHandlers process a ChannelEvent.
ChannelFuture	execute(ChannelPipeline pipeline, java.lang.Runnable task)	Execute the given Runnable later in the io-thread.

Method Detail

eventSunk

void eventSunk(ChannelPipeline pipeline,
               ChannelEvent e)
        throws java.lang.Exception

Invoked by ChannelPipeline when a downstream ChannelEvent has reached its terminal (the head of the pipeline).

Throws:

java.lang.Exception

exceptionCaught

void exceptionCaught(ChannelPipeline pipeline,
                     ChannelEvent e,
                     ChannelPipelineException cause)
              throws java.lang.Exception

Invoked by ChannelPipeline when an exception was raised while one of its ChannelHandlers process a ChannelEvent.

Throws:

java.lang.Exception

execute

ChannelFuture execute(ChannelPipeline pipeline,
                      java.lang.Runnable task)

Execute the given Runnable later in the io-thread. Some implementation may not support this and just execute it directly.