Will be removed in 3.1.0. There is no general replacement for BlockingSink in 3.1 but its major
user FluxProcessor now offers FluxProcessor.sink() that directly exposes
FluxSink. In general the blocking publishing methods here can be directly
addressed via the behavior of FluxProcessor.sink() in a safer way. There is
also FluxSink.onRequest(LongConsumer) available to now proactively deal with
backpressure even in the context of producing to an arbitrary processor.

submit

Blocking Subscriber.onNext(Object) call with a timed wait on backpressure. A retry predicate will
evaluate when a timeout occurs, returning true will re-schedule an emission while false will drop the signal.

Parameters:

data - the data to signal

timeout - the maximum waiting time in milliseconds before giving up

dropPredicate - the dropped signal callback evaluating if retry should occur or not

submit

Blocking Subscriber.onNext(Object) call with a timed wait on backpressure. A retry predicate will
evaluate when a timeout occurs, returning true will re-schedule an emission while false will drop the signal.

Parameters:

data - the data to signal

timeout - the maximum waiting time in given unit before giving up

unit - the waiting time unit

dropPredicate - the dropped signal callback evaluating if retry should occur or not