submit tasks for execution. Consumers take
completed tasks and process their results in the order they
complete. A CompletionService can for example be used to
manage asynchronous I/O, in which tasks that perform reads are
submitted in one part of a program or system, and then acted upon
in a different part of the program when the reads complete,
possibly in a different order than they were requested.
Typically, a CompletionService relies on a separate
Executor to actually execute the tasks, in which case the
CompletionService only manages an internal completion
queue. The ExecutorCompletionService class provides an
implementation of this approach.
Memory consistency effects: Actions in a thread prior to
submitting a task to a CompletionService
happen-before
actions taken by that task, which in turn happen-before
actions following a successful return from the corresponding take().
| Modifier and Type | Method and Description |
|---|---|
| public Future | Returns: the Future representing the next completed task, ornull if none are presentRetrieves and removes the Future representing the next
completed task, or |
| public Future | Returns: the Future representing the next completed task ornull if the specified waiting time elapses
before one is presenthow long to wait before giving up, in units of
timeout, TimeUnit unita unit)TimeUnit determining how to interpret the
timeout parameterRetrieves and removes the Future representing the next completed task, waiting if necessary up to the specified wait time if none are yet present. |
| public Future | |
| public Future | Returns: a Future representing pending completion of the task, and whoseget() method will return the given
result value upon completionthe task to submit task, V the result to return upon successful completion result)Submits a Runnable task for execution and returns a Future representing that task. |
| public Future | Returns: the Future representing the next completed taskRetrieves and removes the Future representing the next completed task, waiting if none are yet present. |
| poll | back to summary |
|---|---|
| public Future Retrieves and removes the Future representing the next
completed task, or
| |
| poll | back to summary |
|---|---|
| public Future Retrieves and removes the Future representing the next completed task, waiting if necessary up to the specified wait time if none are yet present.
| |
| submit | back to summary |
|---|---|
| public Future Submits a value-returning task for execution and returns a Future representing the pending results of the task. Upon completion, this task may be taken or polled.
| |
| submit | back to summary |
|---|---|
| public Future Submits a Runnable task for execution and returns a Future representing that task. Upon completion, this task may be taken or polled.
| |
| take | back to summary |
|---|---|
| public Future Retrieves and removes the Future representing the next completed task, waiting if none are yet present.
| |