On Wed, Sep 22, 2021 at 9:06 PM Mark Miller <[email protected]> wrote: ...
> Zk alerts us when it losses a connection via callback. When the connection > is back, another callback. An unlimited number of locations trying to work > this out on there own is terrible zk. In an ideal world, everything enters > a zk quiete mode and re-engaged when zk says hello again. A simpler shorter > term improvement is to simply sink all the zk calls when they hit the zk > connection manager and don’t let them go until the connection is restored. > While I don't tend to work on this stuff, I want to understand the essence of your point. Are you basically recommending that our ZK interactions should all go through one instance of a ZK connection manager class that can keep track of ZK's connection state?
