See: Description
Class | Description |
---|---|
AbstractTrafficShapingHandler |
AbstractTrafficShapingHandler allows to limit the global bandwidth
(see
GlobalTrafficShapingHandler ) or per session
bandwidth (see ChannelTrafficShapingHandler ), as traffic shaping. |
ChannelTrafficShapingHandler |
This implementation of the
AbstractTrafficShapingHandler is for channel
traffic shaping, that is to say a per channel limitation of the bandwidth. |
GlobalTrafficShapingHandler |
This implementation of the
AbstractTrafficShapingHandler is for global
traffic shaping, that is to say a global limitation of the bandwidth, whatever
the number of opened channels. |
TrafficCounter |
TrafficCounter is associated with
AbstractTrafficShapingHandler . |
The main goal of this package is to allow to shape the traffic (bandwidth limitation), but also to get statistics on how many bytes are read or written. Both functions can be active or inactive (traffic or statistics).
Two classes implement this behavior:
TrafficCounter
: this class implements the counters
needed by the handlers. It can be accessed to get some extra information like the read or
write bytes since last check, the read and write bandwidth from last check...AbstractTrafficShapingHandler
: this abstract class
implements the kernel of the traffic shaping. It could be extended to fit your needs. Two
classes are proposed as default implementations: see
ChannelTrafficShapingHandler
and
GlobalTrafficShapingHandler
respectively for
Channel traffic shaping and Global traffic shaping.MemoryAwareThreadPoolExecutor
in your pipeline.MemoryAwareThreadPoolExecutor
(either non ordered or
OrderedMemoryAwareThreadPoolExecutor
) in your pipeline
when you want to use this feature with some real traffic shaping, since it will allow to relax the constraint on
NioWorker to do other jobs if necessary.ObjectSizeEstimator
can be passed at construction to specify what
is the size of the object to be read or write accordingly to the type of
object. If not specified, it will used the DefaultObjectSizeEstimator
implementation.Standard use could be as follow:
AbstractTrafficShapingHandler
.AbstractTrafficShapingHandler
or directly using the method configure of TrafficCounter
.So in your application you will create your own TrafficShapingHandler and set the values to fit your needs.
XXXXXTrafficShapingHandler myHandler = new XXXXXTrafficShapingHandler(timer);Note that a new ChannelTrafficShapingHandler
must be
created for each new channel, but only one GlobalTrafficShapingHandler
must be created for all channels.
Note also that you can create different GlobalTrafficShapingHandler if you want to separate classes of channels (for instance either from business point of view or from bind address point of view).
Copyright © 2008-2014 The Netty Project. All Rights Reserved.