@rtyler this is meant to be the first refactoring. the idea was/is to have only one treeWatcher which uses the switch to dispatch the events on three different implementations - broker, standard, spout
the implementation get picked by the base-path if the event.
unfortunately I did not get the ok to proceed here and I am not sure if I find "free" time to finish it.
anyways with this patch brokers can come and go anytime now. the same is needed for consumers and probably topics to have Maps and Sets grow and shrink over time and reflect the current status of the system.
@rtyler this is meant to be the first refactoring. the idea was/is to have only one treeWatcher which uses the switch to dispatch the events on three different implementations - broker, standard, spout
the implementation get picked by the base-path if the event.
unfortunately I did not get the ok to proceed here and I am not sure if I find "free" time to finish it.
anyways with this patch brokers can come and go anytime now. the same is needed for consumers and probably topics to have Maps and Sets grow and shrink over time and reflect the current status of the system.