[SERVER-35779] Add back-propagating cancellation to Future Created: 25/Jun/18 Updated: 06/Dec/22 Resolved: 24/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Sprint: | Platforms 2018-07-02, Platforms 2018-07-16 | ||||||||
| Participants: | |||||||||
| Description |
|
This allows a holder of a Future to indicate that they are not interested in the result anymore and to attempt to prevent more work from happening. This is distinct from |
| Comments |
| Comment by Mira Carey [ 24/Apr/19 ] |
|
Closing this due to a lack of feasibility |
| Comment by Mathias Stearn [ 25/Jun/18 ] |
|
We are promoting this from phase 3 to phase 2 because it greatly simplifies correctly usage of futurized continuations with timeouts. |