Open wlabarron opened 2 years ago
Do you think this should this be global (config based) or per-client? Alternatively, an option to bypass the timeout in the event something extraordinary is happening?
Perhaps a happy-medium could be per-client, with a default value set in global config? That makes it quick to set up in normal contexts, but at setup time offers a clear reminder of timeout feature and a path to fix it before it becomes a problem. It would avoid someone finding out about the timeout at (say) 6am mid-event, or alternatively being confused as to why they randomly, periodically disconnect.
Instead of timeouts after a number of seconds, the timeout could happen at a given time of day. By setting it to 6am or something similar when the venue is always closed, it would reduce the chance of a lease expiring mid-event.