Processor
with backpressure support.See: Description
Class | Description |
---|---|
ExecutorPoweredProcessor<IN,OUT> |
A base processor used by executor backed processors to take care of their ExecutorService
|
MutableSignal<T> | |
ReactorProcessor<IN,OUT> |
A base processor
|
RingBufferProcessor<E> |
An implementation of a RingBuffer backed message-passing Processor.
|
RingBufferWorkProcessor<E> |
An implementation of a RingBuffer backed message-passing WorkProcessor.
|
Enum | Description |
---|---|
MutableSignal.Type |
Exception | Description |
---|---|
CancelException |
An exception signal from downstream subscribers consuming data when their state is denying any additional event.
|
InsufficientCapacityException |
Exception thrown when the it is not possible to dispatch a signal a
Dispatcher . |
Processor
with backpressure support.
Unlike Dispatcher
, these components will be unique and bound to a given stream of data.
A Processor
will manage its own thread(s), one by Subscriber
.
The message-passing will be implementation dependant, e.g. using a RingBuffer
.
Usually, the boundary will be implemented with a queue-based event dispatching and the Reactive Stream contract will
offer control over the available backlog. Long.MAX demand will however switch off the contract and rely on the impl
coordination strategy to back-off, like the RingBuffer waiting strategy, to slow down the Processor publisher.
These Processors are typically expansive to create, best to consider a few places to use them rather than creating them recurly.Copyright © 2017. All rights reserved.