Timeline for Design approach for continuous, time-aware processing of records
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2017 at 21:25 | comment | added | Kwebble | With this solution I would have the scheduling service request the participants from the source when it is time to send the notifications, to reduce the need to sync. | |
| Aug 26, 2017 at 20:51 | comment | added | Caleb | This solution is also good. It would be worth noting that it will require more "syncing" code to keep false notifications from being sent. (Such as when an event is "canceled") | |
| May 28, 2017 at 18:50 | review | First posts | |||
| Jun 27, 2017 at 18:47 | |||||
| May 28, 2017 at 18:43 | history | answered | Artur Wierzbicki | CC BY-SA 3.0 |