public class DAISYCHAIN extends Protocol
| Modifier and Type | Class and Description |
|---|---|
static class |
DAISYCHAIN.DaisyHeader |
| Modifier and Type | Field and Description |
|---|---|
protected java.util.concurrent.Executor |
default_pool |
protected Address |
local_addr |
int |
msgs_forwarded |
int |
msgs_sent |
protected Address |
next |
protected java.util.concurrent.Executor |
oob_pool |
protected boolean |
running |
protected int |
view_size |
after_creation_hook, down_prot, ergonomics, id, log, name, stack, stats, up_prot| Constructor and Description |
|---|
DAISYCHAIN() |
| Modifier and Type | Method and Description |
|---|---|
java.lang.Object |
down(Event evt)
An event is to be sent down the stack.
|
protected void |
handleView(View view) |
void |
init()
Called after instance has been created (null constructor) and before protocol is started.
|
void |
resetStats() |
void |
start()
This method is called on a
Channel.connect(String). |
void |
stop()
This method is called on a
Channel.disconnect(). |
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, afterCreationHook, destroy, dumpStats, enableStats, getConfigurableObjects, getDownProtocol, getDownServices, getId, getIdsAbove, getLevel, getLog, getName, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getUpServices, getValue, isErgonomics, level, parse, printStats, providedDownServices, providedUpServices, requiredDownServices, requiredUpServices, resetStatistics, setDownProtocol, setErgonomics, setId, setLevel, setProtocolStack, setSocketFactory, setUpProtocol, setValue, setValues, statsEnabledprotected volatile Address local_addr
protected volatile Address next
protected int view_size
protected java.util.concurrent.Executor default_pool
protected java.util.concurrent.Executor oob_pool
protected volatile boolean running
public int msgs_forwarded
public int msgs_sent
public void resetStats()
resetStats in class Protocolpublic void init()
throws java.lang.Exception
Protocolpublic void start()
throws java.lang.Exception
ProtocolChannel.connect(String). Starts work.
Protocols are connected and queues are ready to receive events.
Will be called from bottom to top. This call will replace
the START and START_OK events.start in class Protocoljava.lang.Exception - Thrown if protocol cannot be started successfully. This will cause the ProtocolStack
to fail, so Channel.connect(String) will throw an exceptionpublic void stop()
ProtocolChannel.disconnect(). Stops work (e.g. by closing multicast socket).
Will be called from top to bottom. This means that at the time of the method invocation the
neighbor protocol below is still working. This method will replace the
STOP, STOP_OK, CLEANUP and CLEANUP_OK events. The ProtocolStack guarantees that
when this method is called all messages in the down queue will have been flushedpublic java.lang.Object down(Event evt)
Protocoldown_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)
Protocoldown_prot.down() or c) the event (or another event) is sent up
the stack using up_prot.up().public void up(MessageBatch batch)
ProtocolMessageBatch. 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(org.jgroups.Message)), and - if true - calls Protocol.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.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.protected void handleView(View view)
Copyright © 1998-2020 Red Hat. All Rights Reserved.