Class DELAY
- All Implemented Interfaces:
Lifecycle
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).
- Author:
- Bela Ban, Sanne Grinovero, Matej Cimbora
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected booleanprotected org.jgroups.protocols.DELAY.DelayedMessageHandlerprotected DelayQueue<org.jgroups.protocols.DELAY.DelayedMessage> protected intprotected intprotected intprotected intFields inherited from class Protocol
after_creation_hook, down_prot, ergonomics, id, local_addr, log, policies, preview_warning, stack, stats, up_prot -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoiddestroy()This method is called on aJChannel.close().A message is sent down the stack.intintintintvoidinit()Called after a protocol has been created and before the protocol is started.voidsetInDelay(int in_delay) voidsetInDelayNanos(int in_delay_nanos) voidsetOutDelay(int out_delay) voidsetOutDelayNanos(int out_delay_nanos) A single message was received.voidup(MessageBatch batch) Sends up a multiple messages in aMessageBatch.Methods inherited from class Protocol
accept, addPolicy, addr, addr, afterCreationHook, down, down, enableStats, getAddress, getComponents, getDownProtocol, getDownServices, getId, getIdsAbove, getLevel, getLog, getName, getPolicies, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getUpServices, getValue, isErgonomics, level, parse, policies, previewWarning, previewWarning, providedDownServices, providedUpServices, removePolicy, requiredDownServices, requiredUpServices, resetStatistics, resetStats, setAddress, setDownProtocol, setErgonomics, setId, setLevel, setPolicies, setProtocolStack, setSocketFactory, setUpProtocol, setValue, start, statsEnabled, stop, toString, up
-
Field Details
-
in_delay
protected int in_delay -
out_delay
protected int out_delay -
in_delay_nanos
protected int in_delay_nanos -
out_delay_nanos
protected int out_delay_nanos -
constant_delay
protected boolean constant_delay -
delayed_message_handler
protected org.jgroups.protocols.DELAY.DelayedMessageHandler delayed_message_handler -
delayed_messages
-
-
Constructor Details
-
DELAY
public DELAY()
-
-
Method Details
-
getInDelay
public int getInDelay() -
setInDelay
public void setInDelay(int in_delay) -
getOutDelay
public int getOutDelay() -
setOutDelay
public void setOutDelay(int out_delay) -
getInDelayNanos
public int getInDelayNanos() -
setInDelayNanos
public void setInDelayNanos(int in_delay_nanos) -
getOutDelayNanos
public int getOutDelayNanos() -
setOutDelayNanos
public void setOutDelayNanos(int out_delay_nanos) -
init
Description copied from class:ProtocolCalled after a protocol has been created and before the protocol is started. Attributes are already set. Other protocols are not yet connected and events cannot yet be sent. -
destroy
-
down
-
up
-
up
Description copied from class:ProtocolSends up a multiple messages in aMessageBatch. 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 - callsProtocol.up(org.jgroups.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.iterator(Predicate)), 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.
-