All Downloads are FREE. Search and download functionalities are using the official Maven repository.

rx.Scheduler Maven / Gradle / Ivy

There is a newer version: 1.3.8
Show newest version
/**
 * Copyright 2014 Netflix, Inc.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 * http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package rx;

import java.util.concurrent.TimeUnit;

import rx.annotations.Experimental;
import rx.functions.*;
import rx.internal.schedulers.SchedulerWhen;
import rx.internal.subscriptions.SequentialSubscription;
import rx.schedulers.Schedulers;

/**
 * A {@code Scheduler} is an object that schedules units of work. You can find common implementations of this
 * class in {@link Schedulers}.
 */
public abstract class Scheduler {
/*
 * Why is this an abstract class instead of an interface?
 *
 *  : Java doesn't support extension methods and there are many overload methods needing default
 *    implementations.
 *
 *  : Virtual extension methods aren't available until Java8 which RxJava will not set as a minimum target for
 *    a long time.
 *
 *  : If only an interface were used Scheduler implementations would then need to extend from an
 *    AbstractScheduler pair that gives all of the functionality unless they intend on copy/pasting the
 *    functionality.
 *
 *  : Without virtual extension methods even additive changes are breaking and thus severely impede library
 *    maintenance.
 */

    /**
     * The tolerance for a clock drift in nanoseconds where the periodic scheduler will rebase.
     * 

* The associated system parameter, {@code rx.scheduler.drift-tolerance}, expects its value in minutes. */ static final long CLOCK_DRIFT_TOLERANCE_NANOS; static { CLOCK_DRIFT_TOLERANCE_NANOS = TimeUnit.MINUTES.toNanos( Long.getLong("rx.scheduler.drift-tolerance", 15)); } /** * Retrieves or creates a new {@link Scheduler.Worker} that represents serial execution of actions. *

* When work is completed it should be unsubscribed using {@link Scheduler.Worker#unsubscribe()}. *

* Work on a {@link Scheduler.Worker} is guaranteed to be sequential. * * @return a Worker representing a serial queue of actions to be executed */ public abstract Worker createWorker(); /** * Sequential Scheduler for executing actions on a single thread or event loop. *

* Unsubscribing the {@link Worker} unschedules all outstanding work and allows resources cleanup. */ public abstract static class Worker implements Subscription { /** * Schedules an Action for execution. * * @param action * Action to schedule * @return a subscription to be able to unsubscribe the action (unschedule it if not executed) */ public abstract Subscription schedule(Action0 action); /** * Schedules an Action for execution at some point in the future. *

* Note to implementors: non-positive {@code delayTime} should be regarded as undelayed schedule, i.e., * as if the {@link #schedule(rx.functions.Action0)} was called. * * @param action * the Action to schedule * @param delayTime * time to wait before executing the action; non-positive values indicate an undelayed * schedule * @param unit * the time unit of {@code delayTime} * @return a subscription to be able to unsubscribe the action (unschedule it if not executed) */ public abstract Subscription schedule(final Action0 action, final long delayTime, final TimeUnit unit); /** * Schedules a cancelable action to be executed periodically. This default implementation schedules * recursively and waits for actions to complete (instead of potentially executing long-running actions * concurrently). Each scheduler that can do periodic scheduling in a better way should override this. *

* Note to implementors: non-positive {@code initialTime} and {@code period} should be regarded as * undelayed scheduling of the first and any subsequent executions. * * @param action * the Action to execute periodically * @param initialDelay * time to wait before executing the action for the first time; non-positive values indicate * an undelayed schedule * @param period * the time interval to wait each time in between executing the action; non-positive values * indicate no delay between repeated schedules * @param unit * the time unit of {@code period} * @return a subscription to be able to unsubscribe the action (unschedule it if not executed) */ public Subscription schedulePeriodically(final Action0 action, long initialDelay, long period, TimeUnit unit) { final long periodInNanos = unit.toNanos(period); final long firstNowNanos = TimeUnit.MILLISECONDS.toNanos(now()); final long firstStartInNanos = firstNowNanos + unit.toNanos(initialDelay); final SequentialSubscription first = new SequentialSubscription(); final SequentialSubscription mas = new SequentialSubscription(first); final Action0 recursiveAction = new Action0() { long count; long lastNowNanos = firstNowNanos; long startInNanos = firstStartInNanos; @Override public void call() { action.call(); if (!mas.isUnsubscribed()) { long nextTick; long nowNanos = TimeUnit.MILLISECONDS.toNanos(now()); // If the clock moved in a direction quite a bit, rebase the repetition period if (nowNanos + CLOCK_DRIFT_TOLERANCE_NANOS < lastNowNanos || nowNanos >= lastNowNanos + periodInNanos + CLOCK_DRIFT_TOLERANCE_NANOS) { nextTick = nowNanos + periodInNanos; /* * Shift the start point back by the drift as if the whole thing * started count periods ago. */ startInNanos = nextTick - (periodInNanos * (++count)); } else { nextTick = startInNanos + (++count * periodInNanos); } lastNowNanos = nowNanos; long delay = nextTick - nowNanos; mas.replace(schedule(this, delay, TimeUnit.NANOSECONDS)); } } }; first.replace(schedule(recursiveAction, initialDelay, unit)); return mas; } /** * Gets the current time, in milliseconds, according to this Scheduler. * * @return the scheduler's notion of current absolute time in milliseconds */ public long now() { return System.currentTimeMillis(); } } /** * Gets the current time, in milliseconds, according to this Scheduler. * * @return the scheduler's notion of current absolute time in milliseconds */ public long now() { return System.currentTimeMillis(); } /** * Allows the use of operators for controlling the timing around when * actions scheduled on workers are actually done. This makes it possible to * layer additional behavior on this {@link Scheduler}. The only parameter * is a function that flattens an {@link Observable} of {@link Observable} * of {@link Completable}s into just one {@link Completable}. There must be * a chain of operators connecting the returned value to the source * {@link Observable} otherwise any work scheduled on the returned * {@link Scheduler} will not be executed. *

* When {@link Scheduler#createWorker()} is invoked a {@link Observable} of * {@link Completable}s is onNext'd to the combinator to be flattened. If * the inner {@link Observable} is not immediately subscribed to an calls to * {@link Worker#schedule} are buffered. Once the {@link Observable} is * subscribed to actions are then onNext'd as {@link Completable}s. *

* Finally the actions scheduled on the parent {@link Scheduler} when the * inner most {@link Completable}s are subscribed to. *

* When the {@link Worker} is unsubscribed the {@link Completable} emits an * onComplete and triggers any behavior in the flattening operator. The * {@link Observable} and all {@link Completable}s give to the flattening * function never onError. *

* Limit the amount concurrency two at a time without creating a new fix * size thread pool: * *

     * Scheduler limitSched = Schedulers.computation().when(workers -> {
     * 	// use merge max concurrent to limit the number of concurrent
     * 	// callbacks two at a time
     * 	return Completable.merge(Observable.merge(workers), 2);
     * });
     * 
*

* This is a slightly different way to limit the concurrency but it has some * interesting benefits and drawbacks to the method above. It works by * limited the number of concurrent {@link Worker}s rather than individual * actions. Generally each {@link Observable} uses its own {@link Worker}. * This means that this will essentially limit the number of concurrent * subscribes. The danger comes from using operators like * {@link Observable#zip(Observable, Observable, rx.functions.Func2)} where * subscribing to the first {@link Observable} could deadlock the * subscription to the second. * *

     * Scheduler limitSched = Schedulers.computation().when(workers -> {
     * 	// use merge max concurrent to limit the number of concurrent
     * 	// Observables two at a time
     * 	return Completable.merge(Observable.merge(workers, 2));
     * });
     * 
* * Slowing down the rate to no more than than 1 a second. This suffers from * the same problem as the one above I could find an {@link Observable} * operator that limits the rate without dropping the values (aka leaky * bucket algorithm). * *
     * Scheduler slowSched = Schedulers.computation().when(workers -> {
     * 	// use concatenate to make each worker happen one at a time.
     * 	return Completable.concat(workers.map(actions -> {
     * 		// delay the starting of the next worker by 1 second.
     * 		return Completable.merge(actions.delaySubscription(1, TimeUnit.SECONDS));
     *    }));
     * });
     * 
* * @param a Scheduler and a Subscription * @param combine the function that takes a two-level nested Observable sequence of a Completable and returns * the Completable that will be subscribed to and should trigger the execution of the scheduled Actions. * @return the Scheduler with the customized execution behavior */ @SuppressWarnings("unchecked") @Experimental public S when(Func1>, Completable> combine) { return (S) new SchedulerWhen(combine, this); } }