Package org.apache.qpid.protonj2.engine
Interface EnginePipeline
- All Known Implementing Classes:
ProtonEnginePipeline,ProtonEnginePipelineProxy
public interface EnginePipeline
Pipeline of handlers for Engine work.
-
Method Summary
Modifier and TypeMethodDescriptionaddFirst(String name, EngineHandler handler) Adds the given handler to the front of the pipeline with the given name stored for later lookup or remove operations.addLast(String name, EngineHandler handler) Adds the given handler to the end of the pipeline with the given name stored for later lookup or remove operations.engine()Finds and returns first handler that is found in the pipeline that matches the given name.Fires an engine starting event to each handler in the pipeline.Fires an engine state changed event to each handler in the pipeline.fireFailed(EngineFailedException failure) Fires an engine failed event into eachEngineHandlerin the pipeline indicating that the engine is now failed and should not accept or produce new work.fireRead(ProtonBuffer input) Fires a read event consisting of the givenProtonBufferinto the pipeline starting from the lastEngineHandlerin the pipeline and moving through each until the incoming work is fully processed.fireRead(HeaderEnvelope header) Fires a read event consisting of the givenHeaderEnvelopeinto the pipeline starting from the lastEngineHandlerin the pipeline and moving through each until the incoming work is fully processed.fireRead(IncomingAMQPEnvelope envelope) Fires a read event consisting of the givenIncomingAMQPEnvelopeinto the pipeline starting from the lastEngineHandlerin the pipeline and moving through each until the incoming work is fully processed.fireRead(SASLEnvelope envelope) Fires a read event consisting of the givenSASLEnvelopeinto the pipeline starting from the lastEngineHandlerin the pipeline and moving through each until the incoming work is fully processed.fireWrite(ProtonBuffer buffer, Runnable ioComplete) Fires a write event consisting of the givenProtonBufferinto the pipeline starting from the firstEngineHandlerin the pipeline and moving through each until the outgoing work is fully processed.fireWrite(HeaderEnvelope envelope) Fires a write event consisting of the givenHeaderEnvelopeinto the pipeline starting from the firstEngineHandlerin the pipeline and moving through each until the outgoing work is fully processed.fireWrite(OutgoingAMQPEnvelope envelope) Fires a write event consisting of the givenOutgoingAMQPEnvelopeinto the pipeline starting from the firstEngineHandlerin the pipeline and moving through each until the outgoing work is fully processed.fireWrite(SASLEnvelope envelope) Fires a write event consisting of the givenSASLEnvelopeinto the pipeline starting from the firstEngineHandlerin the pipeline and moving through each until the outgoing work is fully processed.first()last()Removes the first handler that is found in the pipeline that matches the given name.remove(EngineHandler handler) Removes the givenEngineHandlerfrom the pipeline if present.Removes the firstEngineHandlerin the pipeline.Removes the lastEngineHandlerin the pipeline.
-
Method Details
-
engine
Engine engine()- Returns:
- the
Enginethat this pipeline is linked to.
-
addFirst
Adds the given handler to the front of the pipeline with the given name stored for later lookup or remove operations. It is not mandatory that each handler have unique names although if handlers do share a name theremove(String)method will only remove them one at a time starting from the first in the pipeline.- Parameters:
name- The name to assign to the handlerhandler- TheEngineHandlerto add into the pipeline.- Returns:
- this
EnginePipeline. - Throws:
IllegalArgumentException- if name is null or empty or the handler is null
-
addLast
Adds the given handler to the end of the pipeline with the given name stored for later lookup or remove operations. It is not mandatory that each handler have unique names although if handlers do share a name theremove(String)method will only remove them one at a time starting from the first in the pipeline.- Parameters:
name- The name to assign to the handlerhandler- TheEngineHandlerto add into the pipeline.- Returns:
- this
EnginePipeline. - Throws:
IllegalArgumentException- if name is null or empty or the handler is null
-
removeFirst
EnginePipeline removeFirst()Removes the firstEngineHandlerin the pipeline.- Returns:
- this
EnginePipeline.
-
removeLast
EnginePipeline removeLast()Removes the lastEngineHandlerin the pipeline.- Returns:
- this
EnginePipeline.
-
remove
Removes the first handler that is found in the pipeline that matches the given name.- Parameters:
name- The name to search for in the pipeline moving from first to last.- Returns:
- this
EnginePipeline.
-
remove
Removes the givenEngineHandlerfrom the pipeline if present.- Parameters:
handler- The handler instance to remove if contained in the pipeline.- Returns:
- this
EnginePipeline.
-
find
Finds and returns first handler that is found in the pipeline that matches the given name.- Parameters:
name- The name to search for in the pipeline moving from first to last.- Returns:
- the
EngineHandlerthat matches the given name or null if none in the pipeline.
-
first
EngineHandler first()- Returns:
- the first
EngineHandlerin the pipeline or null if empty.
-
last
EngineHandler last()- Returns:
- the last
EngineHandlerin the pipeline or null if empty.
-
firstContext
EngineHandlerContext firstContext()- Returns:
- the first
EngineHandlerContextin the pipeline or null if empty.
-
lastContext
EngineHandlerContext lastContext()- Returns:
- the last
EngineHandlerContextin the pipeline or null if empty.
-
fireEngineStarting
EnginePipeline fireEngineStarting()Fires an engine starting event to each handler in the pipeline. Should be used by the engine implementation to signal its handlers that they should initialize.- Returns:
- this
EnginePipeline.
-
fireEngineStateChanged
EnginePipeline fireEngineStateChanged()Fires an engine state changed event to each handler in the pipeline. Should be used by the engine implementation to signal its handlers that they should respond to the new engine state, e.g. the engine failed or was shutdown.- Returns:
- this
EnginePipeline.
-
fireRead
Fires a read event consisting of the givenProtonBufferinto the pipeline starting from the lastEngineHandlerin the pipeline and moving through each until the incoming work is fully processed. If the read events reaches the head of the pipeline and is not handled by any handler an error is thrown and the engine should enter the failed state.- Parameters:
input- TheProtonBufferto inject into the engine pipeline.- Returns:
- this
EnginePipeline.
-
fireRead
Fires a read event consisting of the givenHeaderEnvelopeinto the pipeline starting from the lastEngineHandlerin the pipeline and moving through each until the incoming work is fully processed. If the read events reaches the head of the pipeline and is not handled by any handler an error is thrown and the engine should enter the failed state.- Parameters:
header- TheHeaderEnvelopeto inject into the engine pipeline.- Returns:
- this
EnginePipeline.
-
fireRead
Fires a read event consisting of the givenSASLEnvelopeinto the pipeline starting from the lastEngineHandlerin the pipeline and moving through each until the incoming work is fully processed. If the read events reaches the head of the pipeline and is not handled by any handler an error is thrown and the engine should enter the failed state.- Parameters:
envelope- TheSASLEnvelopeto inject into the engine pipeline.- Returns:
- this
EnginePipeline.
-
fireRead
Fires a read event consisting of the givenIncomingAMQPEnvelopeinto the pipeline starting from the lastEngineHandlerin the pipeline and moving through each until the incoming work is fully processed. If the read events reaches the head of the pipeline and is not handled by any handler an error is thrown and the engine should enter the failed state.- Parameters:
envelope- TheIncomingAMQPEnvelopeto inject into the engine pipeline.- Returns:
- this
EnginePipeline.
-
fireWrite
Fires a write event consisting of the givenHeaderEnvelopeinto the pipeline starting from the firstEngineHandlerin the pipeline and moving through each until the outgoing work is fully processed. If the write events reaches the tail of the pipeline and is not handled by any handler an error is thrown and the engine should enter the failed state. It is expected that after the fire write method returns the givenHeaderEnvelopewill have been written or if held for later the object must be copied.- Parameters:
envelope- TheHeaderEnvelopeto inject into the engine pipeline.- Returns:
- this
EnginePipeline.
-
fireWrite
Fires a write event consisting of the givenOutgoingAMQPEnvelopeinto the pipeline starting from the firstEngineHandlerin the pipeline and moving through each until the outgoing work is fully processed. If the write events reaches the tail of the pipeline and is not handled by any handler an error is thrown and the engine should enter the failed state. It is expected that after the fire write method returns the givenOutgoingAMQPEnvelopewill have been written or if held for later the object must be copied. When the payload given exceeds the maximum allowed frame size when encoded into an outbound frame the encoding handler should either throw an error in the case that the performative being written cannot truncate its payload or should invoke the payload to large handler of the envelope before re-encoding the outbound performative and truncating the payload.- Parameters:
envelope- TheOutgoingAMQPEnvelopeto inject into the engine pipeline.- Returns:
- this
EnginePipeline.
-
fireWrite
Fires a write event consisting of the givenSASLEnvelopeinto the pipeline starting from the firstEngineHandlerin the pipeline and moving through each until the outgoing work is fully processed. If the write events reaches the tail of the pipeline and is not handled by any handler an error is thrown and the engine should enter the failed state. It is expected that after the fire write method returns the givenSASLEnvelopewill have been written or if held for later the object must be copied.- Parameters:
envelope- TheSASLEnvelopeto inject into the engine pipeline.- Returns:
- this
EnginePipeline.
-
fireWrite
Fires a write event consisting of the givenProtonBufferinto the pipeline starting from the firstEngineHandlerin the pipeline and moving through each until the outgoing work is fully processed. If the write events reaches the tail of the pipeline and is not handled by any handler an error is thrown and the engine should enter the failed state.- Parameters:
buffer- TheProtonBufferto inject into the engine pipeline.ioComplete- An optional callback that should be signaled when the underlying transport complete the I/O write- Returns:
- this
EnginePipeline.
-
fireFailed
Fires an engine failed event into eachEngineHandlerin the pipeline indicating that the engine is now failed and should not accept or produce new work.- Parameters:
failure- The cause of the engine failure.- Returns:
- this
EnginePipeline.
-