public class DELAY extends Protocol
Incoming messages can be delayed independently from outgoing messages (or not delayed at all).
This protocol should be inserted directly above the transport protocol (e.g. UDP).
限定符和类型 | 字段和说明 |
---|---|
protected int |
in_delay |
protected int |
in_delay_nanos |
protected int |
out_delay |
protected int |
out_delay_nanos |
构造器和说明 |
---|
DELAY() |
限定符和类型 | 方法和说明 |
---|---|
java.lang.Object |
down(Event evt)
An event is to be sent down the stack.
|
int |
getInDelay() |
int |
getInDelayNanos() |
int |
getOutDelay() |
int |
getOutDelayNanos() |
void |
setInDelay(int in_delay) |
void |
setInDelayNanos(int in_delay_nanos) |
void |
setOutDelay(int out_delay) |
void |
setOutDelayNanos(int out_delay_nanos) |
java.lang.Object |
up(Event evt)
An event was received from the layer below.
|
void |
up(MessageBatch batch)
Sends up a multiple messages in a
MessageBatch . |
accept, destroy, dumpStats, enableStats, getConfigurableObjects, getDownProtocol, getDownServices, getId, getIdsAbove, getLevel, getName, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getUpServices, getValue, init, isErgonomics, level, parse, printStats, providedDownServices, providedUpServices, requiredDownServices, requiredUpServices, resetStatistics, resetStats, setDownProtocol, setErgonomics, setId, setLevel, setProtocolStack, setSocketFactory, setUpProtocol, setValue, setValues, start, statsEnabled, stop
protected int in_delay
protected int out_delay
protected int in_delay_nanos
protected int out_delay_nanos
public int getInDelay()
public void setInDelay(int in_delay)
public int getOutDelay()
public void setOutDelay(int out_delay)
public int getInDelayNanos()
public void setInDelayNanos(int in_delay_nanos)
public int getOutDelayNanos()
public void setOutDelayNanos(int out_delay_nanos)
public java.lang.Object down(Event evt)
Protocol
down_prot.down()
. In case of a GET_ADDRESS event (which tries to
retrieve the stack's address from one of the bottom layers), the layer may need to send
a new response event back up the stack using up_prot.up()
.public java.lang.Object up(Event evt)
Protocol
down_prot.down()
or c) the event (or another event) is sent up
the stack using up_prot.up()
.public void up(MessageBatch batch)
Protocol
MessageBatch
. The sender of the batch is always the same, and so is the
destination (null == multicast messages). Messages in a batch can be OOB messages, regular messages, or mixed
messages, although the transport itself will create initial MessageBatches that contain only either OOB or
regular messages.
The default processing below sends messages up the stack individually, based on a matching criteria
(calling Protocol.accept(Message)
), and - if true - calls Protocol.up(Event)
for that message and removes the message. If the batch is not empty, it is passed up, or else it is dropped.
Subclasses should check if there are any messages destined for them (e.g. using
MessageBatch.getMatchingMessages(short, boolean)
), then possibly remove and process them and finally pass
the batch up to the next protocol. Protocols can also modify messages in place, e.g. ENCRYPT could decrypt all
encrypted messages in the batch, not remove them, and pass the batch up when done.