Uses of Package
io.netty5.handler.traffic

Packages that use io.netty5.handler.traffic

Package	Description
io.netty5.handler.traffic	Implementation of a Traffic Shaping Handler and Dynamic Statistics.

Classes in io.netty5.handler.traffic used by io.netty5.handler.traffic

Class	Description
AbstractTrafficShapingHandler	AbstractTrafficShapingHandler allows to limit the global bandwidth (see GlobalTrafficShapingHandler) or per session bandwidth (see ChannelTrafficShapingHandler), as traffic shaping.
GlobalChannelTrafficShapingHandler	This implementation of the AbstractTrafficShapingHandler 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.
TrafficCounter	Counts the number of read and written bytes for rate-limiting traffic.