Class HDRS

  • All Implemented Interfaces:
    Lifecycle

    public class HDRS
    extends Protocol
    Prints the headers of all sent or received messages
    • Field Detail

      • print_down

        protected volatile boolean print_down
      • print_up

        protected volatile boolean print_up
      • filter

        protected java.util.function.Predicate<Message> filter
    • Constructor Detail

      • HDRS

        public HDRS()
    • Method Detail

      • printUp

        public boolean printUp()
      • printUp

        public HDRS printUp​(boolean b)
      • printDown

        public boolean printDown()
      • printDown

        public HDRS printDown​(boolean b)
      • filter

        public HDRS filter​(java.util.function.Predicate<Message> f)
      • down

        public java.lang.Object down​(Message msg)
        Description copied from class: Protocol
        A message is sent down the stack. Protocols may examine the message and do something (e.g. add a header) with it, before passing it down.
        Overrides:
        down 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(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