public class VERIFY_SUSPECT extends Protocol implements java.lang.Runnable
| Modifier and Type | Class and Description |
|---|---|
static class |
VERIFY_SUSPECT.VerifyHeader |
| Modifier and Type | Field and Description |
|---|---|
protected java.lang.String |
bind_interface_str |
| Constructor and Description |
|---|
VERIFY_SUSPECT() |
| Modifier and Type | Method and Description |
|---|---|
java.lang.Object |
down(Event evt)
An event is to be sent down the stack.
|
void |
init()
Called after instance has been created (null constructor) and before protocol is started.
|
void |
run()
Will be started when a suspect is added to the suspects hashtable.
|
void |
stop()
This method is called on a
Channel.disconnect(). |
java.lang.Object |
up(Event evt)
An event was received from the layer below.
|
destroy, downThreadEnabled, dumpStats, enableStats, getConfigurableObjects, getDownProtocol, getId, getLevel, getName, getProperties, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getValue, isErgonomics, printStats, providedDownServices, providedUpServices, requiredDownServices, requiredUpServices, resetStats, setDownProtocol, setErgonomics, setId, setLevel, setProperties, setPropertiesInternal, setProperty, setProtocolStack, setSocketFactory, setUpProtocol, setValue, setValues, start, statsEnabled, upThreadEnabledpublic 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 run()
run in interface java.lang.Runnablepublic void init()
throws java.lang.Exception
Protocolpublic 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 flushedCopyright ? 1998-2009 Bela Ban / Red Hat. All Rights Reserved.