Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TaskFuture implementation with transient backing Future instead of cached #51

Open
jonathanaustin opened this issue Apr 29, 2022 · 0 comments
Open

TaskFuture implementation with transient backing Future instead of cached #51

jonathanaustin opened this issue Apr 29, 2022 · 0 comments

Comments

@jonathanaustin
Copy link
Member

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jonathanaustin