Currently we have a class named GossipSettings and a process that parses JSON files to start up the Gossiper.
This was something from the original code fork that that I never used much. I originally forked gossip to use inside a service that already had its own configuration file. We have gotten some contributions on this piece. And the 'here is a file, now start' concept seems easy to grasp for people. The challenge we face code wise is we have a few classes and builders to get Gossip started. Some components, for example the GossipEventListener, are typically defined as a lambda or would be hard to parameterize into configuration. For now I am going with the concept of anything easy to add to the settings I will add but the settings from GossipSettings.json will only be a subset of the features available when constructing from code. Let me know if anyone has any ideas as how to make GossipSettings less manual work. One idea is we can make into a pojo and DOM parse it vs the current SAX style. Thanks, Edward
