[SERVER-35822] Introduce Futurized Event Management Created: 26/Jun/18 Updated: 23/Mar/23 Resolved: 24/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | re-triaged-ticket, service_architecture_future | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
BackgroundThreadClockSource is an ideal place to manage scheduled events ala existing ReactorTimer classes. The BTCS should be able to return a future that will be fulfilled within 10ms of a specified time. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ] |
|
We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket. |
| Comment by Benjamin Caimano (Inactive) [ 26/Jun/18 ] |
|
Makes the interface for timeout events very simple. |
| Comment by Benjamin Caimano (Inactive) [ 26/Jun/18 ] |
|
acm, the first paper is here. The follow up is behind a ieee paywall. |