Feb 7, 2023

The only approach that I can think of that makes sense is to create a timer for each event, register timer cancel with the stop subscriber, and capture the timer in its stop and timeout handlers. This keeps stop responsive and allows for a delay on each manual connect failure and batch connect failure, and won't get reset by any other events. This also allows the session member timer to be removed. Th overhead shouldn't be an issue, as the whole point is intentional idling.