程序包 | 说明 |
---|---|
reactor.core.publisher |
限定符和类型 | 类和说明 |
---|---|
class |
DirectProcessor<T>
已过时。
To be removed in 3.5, prefer clear cut usage of
Sinks . Closest sink
is Sinks.many().multicast().directBestEffort() ,
except it doesn't terminate overflowing downstreams. |
class |
EmitterProcessor<T>
已过时。
To be removed in 3.5. Prefer clear cut usage of
Sinks through
variations of Sinks.many().multicast().onBackpressureBuffer() .
If you really need the subscribe-to-upstream functionality of a Processor , switch
to Sinks.ManyWithUpstream with Sinks.unsafe() variants of Sinks.unsafe().manyWithUpstream() .
This processor was blocking in EmitterProcessor.onNext(Object) . This behaviour can be implemented with the Sinks API by calling
Sinks.Many.tryEmitNext(Object) and retrying, e.g.:
|
class |
ReplayProcessor<T>
已过时。
To be removed in 3.5, prefer clear cut usage of
Sinks through
variations under Sinks.many().replay() . |
class |
UnicastProcessor<T>
已过时。
to be removed in 3.5, prefer clear cut usage of
Sinks through
variations under Sinks.many().unicast() . |
限定符和类型 | 方法和说明 |
---|---|
FluxProcessor<IN,OUT> |
FluxProcessor.serialize()
已过时。
Create a
FluxProcessor that safely gates multi-threaded producer
Subscriber.onNext(Object) . |
static <T> FluxProcessor<org.reactivestreams.Publisher<? extends T>,T> |
FluxProcessor.switchOnNext()
已过时。
should use
Sinks , Sinks.Many.asFlux() and Flux.switchOnNext(Publisher) . To be removed in 3.5.0. |
static <IN,OUT> FluxProcessor<IN,OUT> |
FluxProcessor.wrap(org.reactivestreams.Subscriber<IN> upstream,
org.reactivestreams.Publisher<OUT> downstream)
已过时。
|