Package org.jgroups.protocols

Class NAMING

  • public class NAMING
extends Protocol
    Maintains mappings between addresses and logical names.

    JIRA: https://issues.jboss.org/browse/JGRP-2104

    Since:
    4.0
    Author:
    Bela Ban

    • Field Detail

      • local_addr

        protected Address local_addr

      • view

        protected volatile View view

      • stagger_timeout

        protected long stagger_timeout

    • Constructor Detail

      • NAMING

        public NAMING()

    • Method Detail

      • down

        public java.lang.Object down​(Event evt)
        Description copied from class: Protocol
        An event is to be sent down the stack. A protocol may want to examine its type and perform some action on it, depending on the event's type. If the event is a message MSG, then the protocol may need to add a header to it (or do nothing at all) before sending it down the stack using down_prot.down().
        Overrides:
        down in class Protocol

      • up

        public java.lang.Object up​(Event evt)
        Description copied from class: Protocol
        An event was received from the protocol below. Usually the current protocol will want to examine the event type and - depending on its type - perform some computation (e.g. removing headers from a MSG event type, or updating the internal membership list when receiving a VIEW_CHANGE event). Finally the event is either a) discarded, or b) an event is sent down the stack using down_prot.down() or c) the event (or another event) is sent up the stack using up_prot.up().
        Overrides:
        up in class Protocol

      • up

        public java.lang.Object up​(Message msg)
        Description copied from class: Protocol
        A single message was received. Protocols may examine the message and do something (e.g. add a header) with it before passing it up.
        Overrides:
        up in class Protocol

      • up

        public void up​(MessageBatch batch)
        Description copied from class: Protocol
        Sends up a multiple messages in a 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(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.

        Overrides:
        up in class Protocol
        Parameters:
        batch - The message batch

      • handleCacheRequest

        protected void handleCacheRequest​(Address sender)
        Typically received by the coord, which sends its cache contents to the sender (new joiner). However, we don't send one large message, but rather N messages (1 per cluster member). The reason is that we don't know where in the stack NAMING will be running and therefore cannot assume fragmentation of large messages.

      • handleCacheResponse

        protected void handleCacheResponse​(Message msg)

      • handleEvent

        protected void handleEvent​(Event evt)

      • multicastOwnMapping

        protected void multicastOwnMapping()