In 03dabdd the service will go to sleep after a period of rolling inactivity.
If after that period the user rolls from the app, the service will be restarted and this is fine. However if the user starts a roll and that roll is not yet confirmed just before the service goes to sleep we have an issue.
Basically we need to find a way so the frontend app can notify the service to reset its inactivity timer.
This could probably be done through Internet Process Communication tools like Python OSC.
In 03dabdd the service will go to sleep after a period of rolling inactivity. If after that period the user rolls from the app, the service will be restarted and this is fine. However if the user starts a roll and that roll is not yet confirmed just before the service goes to sleep we have an issue. Basically we need to find a way so the frontend app can notify the service to reset its inactivity timer. This could probably be done through Internet Process Communication tools like Python OSC.