Deprecated API

Contents

• Deprecated Classes
• Deprecated Methods

Deprecated Classes

Class and Description
RunnableCompletable Use Completable.fromRunnable(Runnable).

Deprecated Methods

Method and Description
io.servicetalk.concurrent.api.Completable.idleTimeout(Duration) Use Completable.timeout(Duration).
io.servicetalk.concurrent.api.Single.idleTimeout(Duration) Use Single.timeout(Duration).
io.servicetalk.concurrent.api.Publisher.idleTimeout(Duration) Use Publisher.timeout(Duration)
io.servicetalk.concurrent.api.Completable.idleTimeout(Duration, Executor) Use Completable.timeout(Duration, io.servicetalk.concurrent.Executor).
io.servicetalk.concurrent.api.Single.idleTimeout(Duration, Executor) Use Single.timeout(Duration, io.servicetalk.concurrent.Executor).
io.servicetalk.concurrent.api.Publisher.idleTimeout(Duration, Executor) Use Publisher.timeout(Duration, io.servicetalk.concurrent.Executor).
io.servicetalk.concurrent.api.Completable.idleTimeout(long, TimeUnit) Use Completable.timeout(long, TimeUnit).
io.servicetalk.concurrent.api.Single.idleTimeout(long, TimeUnit) Use Single.timeout(long, TimeUnit).
io.servicetalk.concurrent.api.Publisher.idleTimeout(long, TimeUnit) Use Publisher.timeout(long, TimeUnit).
io.servicetalk.concurrent.api.Completable.idleTimeout(long, TimeUnit, Executor) Use Completable.timeout(long, TimeUnit, io.servicetalk.concurrent.Executor).
io.servicetalk.concurrent.api.Single.idleTimeout(long, TimeUnit, Executor) Use Single.timeout(Duration, io.servicetalk.concurrent.Executor).
io.servicetalk.concurrent.api.Publisher.idleTimeout(long, TimeUnit, Executor) Use Publisher.timeout(long, TimeUnit, io.servicetalk.concurrent.Executor).
io.servicetalk.concurrent.api.Completable.publishAndSubscribeOn(Executor) This operator has been deprecated because of upcoming behavior changes in how offloading via operators is done. Originally offloading for subscribe/subscription was applied at the "bottom" of chain (logically the last operator in the chain closest to the subscriber), and offloading for subscriber was applied at the "top" of the operator chain (logically the first operator in the chain after the async source). The current offloading doesn't respect the order in which the operators are applied, the offloading is the same regardless of where the operators are placed in the chain. However, this behavior will soon change to instead respect operator placement order and apply offloading exactly where the offloading operators are applied in the chain. This change in behavior means that it no longer makes sense to fuse the offloading of publish and subscribe as the location of the operators in the chain will now be significant. Publish and subscribe offloading, when required, will typically be placed in different locations. Use separate, appropriately placed, Completable.subscribeOn(Executor) and Completable.publishOn(Executor) operators instead.
io.servicetalk.concurrent.api.Single.publishAndSubscribeOn(Executor) This operator has been deprecated because of upcoming behavior changes in how offloading via operators is done. Originally offloading for subscribe/subscription was applied at the "bottom" of chain (logically the last operator in the chain closest to the subscriber), and offloading for subscriber was applied at the "top" of the operator chain (logically the first operator in the chain after the async source). The current offloading doesn't respect the order in which the operators are applied, the offloading is the same regardless of where the operators are placed in the chain. However, this behavior will soon change to instead respect operator placement order and apply offloading exactly where the offloading operators are applied in the chain. This change in behavior means that it no longer makes sense to fuse the offloading of publish and subscribe as the location of the operators in the chain will now be significant. Publish and subscribe offloading, when required, will typically be placed in different locations. Use separate, appropriately placed, Single.subscribeOn(Executor) and Single.publishOn(Executor) operators instead.
io.servicetalk.concurrent.api.Publisher.publishAndSubscribeOn(Executor) This operator has been deprecated because of upcoming behavior changes in how offloading via operators is done. Originally offloading for subscribe/subscription was applied at the "bottom" of chain (logically the last operator in the chain closest to the subscriber), and offloading for subscriber was applied at the "top" of the operator chain (logically the first operator in the chain after the async source). The current offloading doesn't respect the order in which the operators are applied, the offloading is the same regardless of where the operators are placed in the chain. However, this behavior will soon change to instead respect operator placement order and apply offloading exactly where the offloading operators are applied in the chain. This change in behavior means that it no longer makes sense to fuse the offloading of publish and subscribe as the location of the operators in the chain will now be significant. Publish and subscribe offloading, when required, will typically be placed in different locations. Use separate, appropriately placed, Publisher.subscribeOn(Executor) and Publisher.publishOn(Executor) operators instead.
io.servicetalk.concurrent.api.Completable.publishAndSubscribeOnOverride(Executor) This method will be removed in a future release. Consider switching to Completable.publishAndSubscribeOn(Executor) and/or using Executor.execute(Runnable) for offloading.
io.servicetalk.concurrent.api.Single.publishAndSubscribeOnOverride(Executor) This method will be removed in a future release. Consider switching to Single.publishAndSubscribeOn(Executor) and/or using Executor.execute(Runnable) for offloading.
io.servicetalk.concurrent.api.Publisher.publishAndSubscribeOnOverride(Executor) This method will be removed in a future release. Consider switching to Publisher.publishAndSubscribeOn(Executor) and/or using Executor.execute(Runnable) for offloading.
io.servicetalk.concurrent.api.Completable.publishOnOverride(Executor) This method will be removed in a future release. Consider switching to Completable.publishOn(Executor) and/or using Executor.execute(Runnable) for offloading.
io.servicetalk.concurrent.api.Single.publishOnOverride(Executor) This method will be removed in a future release. Consider switching to Single.publishOn(Executor) and/or using Executor.execute(Runnable) for offloading.
io.servicetalk.concurrent.api.Publisher.publishOnOverride(Executor) This method will be removed in a future release. Consider switching to Publisher.publishOn(Executor) and/or using Executor.execute(Runnable) for offloading.
io.servicetalk.concurrent.api.Single.recoverWith(Function<? super Throwable, ? extends Single<? extends T>>) Use Single.onErrorResume(Function).
io.servicetalk.concurrent.api.Publisher.recoverWith(Function<Throwable, ? extends Publisher<? extends T>>) Use Publisher.onErrorResume(Function).
io.servicetalk.concurrent.api.Completable.subscribeOnOverride(Executor) This method will be removed in a future release. Consider switching to Completable.subscribeOn(Executor) and/or using Executor.execute(Runnable) for offloading.
io.servicetalk.concurrent.api.Single.subscribeOnOverride(Executor) This method will be removed in a future release. Consider switching to Single.subscribeOn(Executor) and/or using Executor.execute(Runnable) for offloading.
io.servicetalk.concurrent.api.Publisher.subscribeOnOverride(Executor) This method will be removed in a future release. Consider switching to Publisher.subscribeOn(Executor) and/or using Executor.execute(Runnable) for offloading.