Feb 10, 2023

Took care of the retry timer issue today. To do this I implemented a "resubscriber" template. We had one of these (as opposed to the simpler subscriber we have) a long time back, but it was sketchy, so I removed it. With proper use of the strand now, it's straightforward. So you register a handler for notifications, and it can be removed externally by unique id, or by false return from a notification. We have a number of places where this would simply/rationalize things a bit, so I'll apply that soon. But working flawlessly with retry timers, where we now can have a retry timer for each connector/acceptor that might fail. Previously a second failure would fire the handler for the previous timer, so with a network failure it didn't do its job (no real delay). It's working great now.