Skip to content

TaskFuture implementation with transient backing Future instead of cached #51

Description

@jonathanaustin

Provide a TaskFuture implementation that has a transient backing Future instead of a backing CACHE. This does mean the reference to the Future will not survive deserialization/serialization. However, if a project knows the lifecycle of the TaskFuture instance and it will not be deserilaized/serialized then the CACHING option is not required. This also eliminates the overhead to configure the CACHE.

The transient implementation can be the default and if the CACHING option is required then this can be enabled via a runtime property.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions