Package org.jgroups.protocols

Class REVERSE

java.lang.Object
org.jgroups.stack.Protocol
org.jgroups.protocols.REVERSE
All Implemented Interfaces:
Lifecycle
public class REVERSE extends Protocol
Reverses the next N messages that are received. E.g. for N=4, {1,2,3,4,5} will be sent up as {4,3,2,1,5}. Blocks until N messages have been received. Used for testing
Since:
4.1.5

  • Field Details

    • num_msgs_to_reverse

      protected volatile int num_msgs_to_reverse

    • filter

      protected Predicate<Message> filter

    • queue

      protected final Deque<Message> queue

  • Constructor Details

    • REVERSE

      public REVERSE()

  • Method Details

    • numMessagesToReverse

      public int numMessagesToReverse()

    • numMessagesToReverse

      public REVERSE numMessagesToReverse(int n)

    • filter

      public Predicate<Message> filter()

    • filter

      public REVERSE filter(Predicate<Message> f)

    • queuedMessages

      public int queuedMessages()

    • stop

      public void stop()
      Description copied from class: Protocol
      Called on a JChannel.disconnect(); stops work (e.g. by closing multicast socket). Will be called from top to bottom.
      Specified by:
      stop in interface Lifecycle
      Overrides:
      stop in class Protocol

    • up

      public 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(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.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.

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

    • flush

      public REVERSE flush()