Uses of Class
org.jboss.netty.channel.SimpleChannelHandler
Packages that use SimpleChannelHandler
Package
Description
Encoder, decoder and their related message types for HTTP.
Encoder, decoder, session handler and their related message types for the SPDY protocol.
The special-purpose handlers that store an event into an internal queue
instead of propagating the event immediately.
Adds support for read and write timeout and idle connection notification
using a
Timer
.Implementation of a Traffic Shaping Handler and Dynamic Statistics.
-
Uses of SimpleChannelHandler in org.jboss.netty.handler.codec.http
Subclasses of SimpleChannelHandler in org.jboss.netty.handler.codec.httpModifier and TypeClassDescriptionclass
Compresses anHttpMessage
and anHttpChunk
ingzip
ordeflate
encoding while respecting the"Accept-Encoding"
header.class
Encodes the content of the outboundHttpResponse
andHttpChunk
. -
Uses of SimpleChannelHandler in org.jboss.netty.handler.codec.spdy
Subclasses of SimpleChannelHandler in org.jboss.netty.handler.codec.spdyModifier and TypeClassDescriptionclass
SimpleChannelHandler
that takes care of adding the right streamId to theHttpResponse
if one is not present. -
Uses of SimpleChannelHandler in org.jboss.netty.handler.queue
Subclasses of SimpleChannelHandler in org.jboss.netty.handler.queue -
Uses of SimpleChannelHandler in org.jboss.netty.handler.timeout
Subclasses of SimpleChannelHandler in org.jboss.netty.handler.timeoutModifier and TypeClassDescriptionclass
An extendedSimpleChannelHandler
that adds the handler method for anIdleStateEvent
. -
Uses of SimpleChannelHandler in org.jboss.netty.handler.traffic
Subclasses of SimpleChannelHandler in org.jboss.netty.handler.trafficModifier and TypeClassDescriptionclass
AbstractTrafficShapingHandler allows to limit the global bandwidth (seeGlobalTrafficShapingHandler
) or per session bandwidth (seeChannelTrafficShapingHandler
), as traffic shaping.class
This implementation of theAbstractTrafficShapingHandler
is for channel traffic shaping, that is to say a per channel limitation of the bandwidth.class
This implementation of theAbstractTrafficShapingHandler
is for global and per channel traffic shaping, that is to say a global limitation of the bandwidth, whatever the number of opened channels and a per channel limitation of the bandwidth.
This version shall not be in the same pipeline than other TrafficShapingHandler.
The general use should be as follow:
Create your unique GlobalChannelTrafficShapingHandler like:
GlobalChannelTrafficShapingHandler myHandler = new GlobalChannelTrafficShapingHandler(executor);
The executor could be the underlying IO worker pool
pipeline.addLast(myHandler);
Note that this handler has a Pipeline Coverage of "all" which means only one such handler must be created and shared among all channels as the counter must be shared among all channels.
Other arguments can be passed like write or read limitation (in bytes/s where 0 means no limitation) or the check interval (in millisecond) that represents the delay between two computations of the bandwidth and so the call back of the doAccounting method (0 means no accounting at all).
Note that as this is a fusion of both Global and Channel Traffic Shaping, limits are in 2 sets, respectively Global and Channel.
A value of 0 means no accounting for checkInterval.class
This implementation of theAbstractTrafficShapingHandler
is for global traffic shaping, that is to say a global limitation of the bandwidth, whatever the number of opened channels.