OverflowStrategy
Related Docs:
trait OverflowStrategy
| package reactive
A OverflowStrategy specifying that on reaching the maximum size, the pipeline should try to apply back-pressure (i.e.
A OverflowStrategy specifying that on reaching the maximum size, the pipeline should try to apply back-pressure (i.e. it should try delaying the data source in producing more elements, until the the consumer has drained the buffer and space is available).
specifies how many events our buffer can hold before overflowing
A OverflowStrategy specifying that on reaching the maximum size, the current buffer should be dropped completely to make room for new events.
A OverflowStrategy specifying that on reaching the maximum size, the current buffer should be dropped completely to make room for new events.
specifies how many events our buffer can hold before overflowing
A OverflowStrategy specifying that on reaching the maximum size, the pipeline should begin dropping incoming events until the buffer has room in it again and is free to process more elements.
A OverflowStrategy specifying that on reaching the maximum size, the pipeline should begin dropping incoming events until the buffer has room in it again and is free to process more elements.
specifies how many events our buffer can hold before overflowing
A OverflowStrategy specifying that on reaching the maximum size, the currently buffered events should start being dropped in a FIFO order, so the oldest events from the buffer will be dropped first.
A OverflowStrategy specifying that on reaching the maximum size, the currently buffered events should start being dropped in a FIFO order, so the oldest events from the buffer will be dropped first.
specifies how many events our buffer can hold before overflowing
A sub-category of overflow strategies that are synchronous and that represent eviction policies, meaning that on buffer overflows events start being dropped.
A sub-category of overflow strategies that are synchronous and that represent eviction policies, meaning that on buffer overflows events start being dropped. Using these policies one can also signal a message informing downstream of dropped events.
A OverflowStrategy specifying that on reaching the maximum size,
the pipeline should cancel the subscription and send an onError
to the observer(s) downstream.
A OverflowStrategy specifying that on reaching the maximum size,
the pipeline should cancel the subscription and send an onError
to the observer(s) downstream.
specifies how many events our buffer can hold before overflowing
A category of OverflowStrategy for buffers that can be used synchronously, without worrying about back-pressure concerns.
A category of OverflowStrategy for buffers that can be used synchronously, without worrying about back-pressure concerns.
Needed such that buffer policies can safely be used in combination with Channel for publishing. For now, that's all policies except BackPressure, a overflowStrategy that can't work for Channel.
A OverflowStrategy specifying that the buffer is completely unbounded.
A OverflowStrategy specifying that the buffer is completely unbounded. Using this overflowStrategy implies that with a fast data source, the system's memory can be exhausted and the process might blow up on lack of memory.
The default library-wide overflowStrategy used whenever a default argument value is needed.
The default library-wide overflowStrategy used whenever a default argument value is needed. Currently set to BackPressure with a buffer size of 2048.