Package: inet.queueing.contract
ITrafficConditioner
module interfaceThis module interface is implemented by traffic conditioner modules. A traffic conditioner connects one input to one output. It operates in passive mode on its input and in active mode on its output. Packets can be pushed into its input and packets can be pulled from its output. A traffic conditioner can drop, delay and reorder packets, but it doesn't modify packets in any way.
Inheritance diagram
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.
Implemented by
Name | Type | Description |
---|---|---|
LeakyBucket | compound module |
This module implements a parameterizable leaky bucket algorithm. |
OmittedTrafficConditioner | compound module |
This module implements the module given interface and can be used as an omitted optional module that removes itself from the module hierarchy during initialize. |
TokenBucket | compound module |
This module implements a parameterizable token bucket algorithm. |
Used in compound modules
Name | Type | Description |
---|---|---|
EthernetInterface | compound module |
This module represents an Ethernet network interface. |
PppInterface | compound module |
This module implements a PPP network interface. |
TrafficConditionerLayer | compound module | (no description) |
Extends
Name | Type | Description |
---|---|---|
IActivePacketSource | module interface |
This module interface must be implemented by active packet source modules. An active packet source, also called a producer, has one output that must be connected to a passive packet sink module. The active packet source is expected to push packets into the connected passive packet sink over time. |
IPassivePacketSink | module interface |
This module interface must be implemented by passive packet sink modules. A passive packet sink, also called a consumer, has one input that must be connected to an active packet source module. The connected active packet source is expected to push packets into the passive packet sink over time. |
Properties
Name | Value | Description |
---|---|---|
omittedTypename | OmittedTrafficConditioner | |
display | i=block/sink |
Source code
// // This module interface is implemented by traffic conditioner modules. A traffic // conditioner connects one input to one output. It operates in passive mode on // its input and in active mode on its output. Packets can be pushed into its // input and packets can be pulled from its output. A traffic conditioner can // drop, delay and reorder packets, but it doesn't modify packets in any way. // moduleinterface ITrafficConditioner extends IPassivePacketSink, IActivePacketSource { parameters: @omittedTypename(OmittedTrafficConditioner); @display("i=block/downarrow"); }File: src/inet/queueing/contract/ITrafficConditioner.ned