Java.util.concurrent
External
Internal
Overview
Java 5 introduced concurrent collections and thread pools, as part of java.util.concurrent, which is a collection of utility classes to use for concurrent programming.
Callable
package java.util.concurrent;
@FunctionalInterface
public interface Callable<V> {
V call() throws Exception;
}
A java.util.concurrent.Callable instance represents a task that returns a result and may throw an exception. Implementors define a single method with no arguments called call(). The Callable interface is similar to Runnable, in that both are designed for classes whose instances are potentially executed by another thread. The difference between a Runnable and a Callable is that the Runnable does not return a result and cannot throw a checked exception. Callable tasks can be submitted for execution to executors.
Usage pattern:
ExecutorService executor = ...;
final String arg = "something";
Future<String> future = executor.submit(new Callable<String>() {
@Override
public String call() throws Exception {
return arg.toUpperCase();
}
});
String result = future.get();
The Callable has been designated as functional interface in Java 8. Callable instances can be replaced with lambda expressions, the above example is equivalent with:
ExecutorService executor = ...;
final String arg = "something";
Future<String> future = executor.submit(() -> arg.toUpperCase());
String result = future.get();
Future
A Future represents the result of an asynchronous computation. Future instances are returned by executors upon task submission. Having access to the Future instance, the caller may check if the computation is complete, wait for its completion, and retrieve the result of the computation. The result of the computation is retrieved with Future.get(), only when the computation has completed. The call will block if the computation is not ready.
The computation may be cancelled Future.cancel(). Once a computation has completed, the computation cannot be cancelled. Additional methods are provided to determine if the task completed normally or was cancelled. It is possible to use a Future with the only purpose of canceling the task, without any interest in the result. If that is the case, declare types of the form Future<?> and return null as a result of the underlying task.
Executors
Queues
Synchronizers
Include CountDownLatch, Exchanger, etc. There is no "Synchronizer" interface though.
CopyOnWriteArrayList
TODO. Use case: JMX#NotificationEmitter
TODO
- Atomic*
- Java 7 Fork/Join Framework