Timeline for Help architect a timer-based scheduler
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 15, 2021 at 7:03 | answer | added | Bart van Ingen Schenau | timeline score: 1 | |
Aug 14, 2021 at 20:24 | history | edited | xyf | CC BY-SA 4.0 |
added 50 characters in body
|
Aug 14, 2021 at 20:19 | history | edited | xyf | CC BY-SA 4.0 |
added 50 characters in body
|
Aug 14, 2021 at 19:47 | comment | added | xyf |
so basically: 1) timers are created/armed 2) timer callback is triggered for every time expiry: if Timer A expires in 5 seconds, a callback is invoked within a thread. It then writes a certain message to send to a priority queue. 3) priority queue is read in main thread . 4) the read value is written to a message queue which wakes up X process . In basic words, X process is being notified what to do when, and that's what the timer scheduler is doing
|
|
Aug 14, 2021 at 19:41 | comment | added | Ewan | sorry not clear. I mean like input is a list tasks that have to be run every y seconds? output is the the tasks being run and timestamps? | |
Aug 14, 2021 at 19:39 | history | edited | xyf | CC BY-SA 4.0 |
added 55 characters in body
|
Aug 14, 2021 at 19:39 | comment | added | xyf | sorry. @Ewan check this: imgur.com/a/ZDdwIJz. Let me know if it's still not clear | |
Aug 14, 2021 at 19:31 | comment | added | Ewan | you are using lots of undefined terms "request", "timeout expiry", "action" etc. can you give a simple example of input and output | |
Aug 14, 2021 at 19:26 | comment | added | joshp | Did you read about the implementation of cron? en.wikipedia.org/wiki/Cron The History section discusses a similar method with important differences used by popular cron implementations. | |
Aug 14, 2021 at 19:19 | history | edited | xyf | CC BY-SA 4.0 |
deleted 4 characters in body
|
Aug 14, 2021 at 19:10 | review | First posts | |||
Aug 15, 2021 at 1:57 | |||||
Aug 14, 2021 at 19:08 | history | asked | xyf | CC BY-SA 4.0 |