Abstract implementation of ApiFuture that mirrorsAbstractFuture in Guava.

Base class forApiService. Similar to Guava'sAbstractService but redeclared so that Guava can be shaded.

INTERNAL USE ONLY. Adapter from ApiFuture to Guava ListenableFuture.

Static utility methods for theApiFuture interface.

A listener for the various state changes that aApiService goes through in its lifecycle.

All methods are no-ops by default, implementors should override the ones they care about.

Implementation of theApiClock interface, which usesSystem#currentTimeMillis() as time source.

INTERNAL USE ONLY. Adapter from Guava ListenableFuture to ApiFuture.

Default implementation of the ApiClock interface, using call to System.nanoTime().

AnApiFuture whose result can be set. Similar to Guava'sSettableFuture, but redeclared so that Guava could be shaded.

Transforms a value, possibly asynchronously.

It is similar to Guava'sAsyncFunction, redeclared so that Guava can be shaded.

An interface for getting the current value of a high-resolution time source, in nanoseconds.

Clocks other thanNanoClock are typically used only for testing.

This interface is required in addition to Java 8's Clock, because nanoTime is required to compare values with io.grpc.CallOptions.getDeadlineNanoTime().

Legacy version of Function.

It is similar to Guava'sFunction, redeclared so that Guava can be shaded.

A Future that can have a listener added.

Similar to Guava'sListenableFuture, but redeclared so that Guava could be shaded.

A callback for accepting the results of anApiFuture.

It is similar to Guava'sFutureCallback, redeclared so that Guava can be shaded.

An object with an operational state, plus asynchronous#startAsync() and#stopAsync() lifecycle methods to transition between states. Example services include webservers, RPC servers and timers.

The normal lifecycle of a service is:

• NEW ->
• STARTING ->
• RUNNING ->
• STOPPING ->
• TERMINATED

There are deviations from this if there are failures or ifApiService#stopAsync is called before theApiService reaches theRUNNING state. The set of legal transitions form aDAG, therefore every method of the listener will be called at most once. N.B. TheState#FAILED andState#TERMINATED states are terminal states, once a service enters either of these states it cannot ever leave them.

Implementors of this interface are strongly encouraged to extendAbstractApiService which implement this interface and make the threading and state management easier.

Similar to Guava'sService, but redeclared so that Guava could be shaded.

The lifecycle states of a service.

The ordering of theState enum is defined such that if there is a state transition fromA -> B thenA.compareTo(B) < 0. N.B. The converse is not true, i.e. ifA.compareTo(B) < 0 then there isnot guaranteed to be a valid state transitionA -> B.

Indicates a public API that can change at any time, and has no guarantee of API stability and backward-compatibility.

Usage guidelines:

1. This annotation is used only on APIs with public visibility. Internal interfaces should not use it.
2. This annotation should only be added to new APIs. Adding it to an existing API is considered API-breaking.
3. Removing this annotation from an API gives it stable status, assuming the API doesn't have other annotations denoting instability (such asInternalApi orInternalExtensionOnly).

Annotates a program element (class, method, package etc) which is internal to its containing library, not part of the public API, and should not be used by users of the library.

This annotation only makes sense on APIs that are not private. Its existence is necessary because Java does not have a visibility level for code within a compilation unit.

Adding this annotation to an API is considered API-breaking.

Indicates a public API that is stable for callers to use, but has no guarantee of stability for extension. Consequently, the API should only be extended within the package containing the API.

For example:

• An interface marked with this annotation can have new methods added to it.
• A non-final class with this annotation can be marked final.
• A class with this annotation can have new abstract methods added.
• a non-final method with this annotation can be marked final.

The list above is just for illustration purposes and is not exhaustive.

Adding this annotation to an API is considered API-breaking.