[SERVER-35690] Add support for merging timeouts into an existing future Created: 19/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: | Mira Carey | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
Currently it's quite cumbersome to add a timeout that cancels; to a future. It generally involves a shared_ptr control block, an atomic and much sadness. We need something like: funcThatFutures().addTimeout(Duration) |
| Comments |
| Comment by Mira Carey [ 24/Apr/19 ] |
|
Declining because we never found a feasible implementation for future cancellation |