On Thu, Feb 06, 2020 at 11:22:14AM -0800, Chia-I Wu wrote:
The global disable_notify state does not scale well when we start using it in more places and when there are multiple threads. Use command-level bools to control whether to notify or not.
Hmm, I don't like passing around the bool everywhere that much.
How about this alternative approach: Flip the default to NOT kick commands. Have an explicit kick function to request a kick when needed. Maybe automatically kick fenced commands.
cheers, Gerd