To let the UI query service status or receive events, we need two-way gRPC over named pipes. That works now, but only in dev, because the named pipe server started by the service isn't global, hence inaccessible to the UI running in current user's session and not in that of the network service.
Then this can be implemented in the configuration/status UI:
[ ] Up-to-date status (for example grey/red/yellow/green light bulbs for the past 14 days?)
[ ] When running UI in the background (minimized to tray after startup), show notifications:
[ ] "X hours/days synced" after resume/start, but only if ... > 2 hours since last sync
CodeCasterNL
commented
2 years ago
To let the UI query service status or receive events, we need two-way gRPC over named pipes. That works now, but only in dev, because the named pipe server started by the service isn't global, hence inaccessible to the UI running in current user's session and not in that of the network service.
Then this can be implemented in the configuration/status UI: