org.springframework.scheduling

## 接口 SchedulingTaskExecutor

- 所有超级接口:
    org.springframework.core.task.AsyncTaskExecutor, Executor, org.springframework.core.task.TaskExecutor
  所有已知实现类:
    ConcurrentTaskExecutor, ConcurrentTaskScheduler, DefaultManagedTaskExecutor, DefaultManagedTaskScheduler, ThreadPoolTaskExecutor, ThreadPoolTaskScheduler

      public interface SchedulingTaskExecutor
      extends org.springframework.core.task.AsyncTaskExecutor

  A `TaskExecutor` extension exposing scheduling characteristics that are relevant to potential task submitters.

  Scheduling clients are encouraged to submit `Runnables` that match the exposed preferences of the `TaskExecutor` implementation in use.

  Note: `SchedulingTaskExecutor` implementations are encouraged to also implement the `AsyncListenableTaskExecutor` interface. This is not required due to the dependency on Spring 4.0's new `ListenableFuture` interface, which would make it impossible for third-party executor implementations to remain compatible with both Spring 4.0 and Spring 3.x.

  从以下版本开始:
    2.0
  作者:
    Juergen Hoeller
  另请参阅:
    `SchedulingAwareRunnable`, `TaskExecutor`, `org.springframework.scheduling.commonj.WorkManagerTaskExecutor`

- - ### 字段概要

    - ### 从接口继承的字段 org.springframework.core.task.AsyncTaskExecutor

      `TIMEOUT_IMMEDIATE, TIMEOUT_INDEFINITE`

  - ### 方法概要

    所有方法 实例方法 抽象方法
    限定符和类型 | 方法和说明
    --- | ---
    `boolean` | `prefersShortLivedTasks()` Does this `TaskExecutor` prefer short-lived tasks over long-lived tasks?

    - ### 从接口继承的方法 org.springframework.core.task.AsyncTaskExecutor

      `execute, submit, submit`

    - ### 从接口继承的方法 org.springframework.core.task.TaskExecutor

      `execute`

- - ### 方法详细资料

    - #### prefersShortLivedTasks

          boolean prefersShortLivedTasks()

      Does this `TaskExecutor` prefer short-lived tasks over long-lived tasks?

      A `SchedulingTaskExecutor` implementation can indicate whether it prefers submitted tasks to perform as little work as they can within a single task execution. For example, submitted tasks might break a repeated loop into individual subtasks which submit a follow-up task afterwards (if feasible).

      This should be considered a hint. Of course `TaskExecutor` clients are free to ignore this flag and hence the `SchedulingTaskExecutor` interface overall. However, thread pools will usually indicated a preference for short-lived tasks, to be able to perform more fine-grained scheduling.

      返回:
        `true` if this `TaskExecutor` prefers short-lived tasks