ByteToObjectStage

Method that decodes ByteBuffers to objects. None reflects not enough data to decode a message Any unused data in the ByteBuffer will be recycled and available for the next read.

WARNING: don't count on the underlying array of the ByteBuffer. This uses the slice method, which could preserve access to the buffer, but mess with the various positions.

Encode objects to buffers

Write a collection of outbound messages to the pipeline with a timeout

Write a collection of outbound messages to the pipeline

Write a single outbound message to the pipeline with a timeout

Write a single outbound message to the pipeline

Find the next inbound Stage of type C, if it exists.

Find the next outbound Stage with the given name, if it exists.

Find the next outbound Stage of type C, if it exists.

Find the next outbound Stage with the given name, if it exists.

Receives inbound commands Override to capture commands.

Remove this MidStage from the pipeline

Replace this MidStage with the provided MidStage of the same type

Replace all remaining inbound Stages of the pipeline, not including this Stage.

Replace all downstream Stages, including this Stage.

If this was a MidStage, its inbound element is notified via a Disconnected Command.

Send a command to the next inbound Stage of the pipeline

Insert the MidStage after this

Insert the MidStage before this Stage

Shuts down the stage, deallocating resources, etc.

It will be called when the stage receives a Disconnected command unless inboundCommand is overridden. This method should not send or Disconnected commands.

It is possible that this will not be called due to failure of other stages to propagate shutdown commands. Conversely, it is also possible for this to be called more than once due to the reception of multiple shutdown commands. It is therefore recommended that the method be idempotent.

Start the stage, allocating resources etc.

This method should not effect other stages by sending commands etc unless it creates them. It is not impossible that the stage will receive other commands besides Connected before this method is called. It is not impossible for this method to be called multiple times by misbehaving stages. It is therefore recommended that the method be idempotent.