Hi All,
Having started to use Vysper for sometime, I am very interested in
contributing to the project, I was going through the core components of
vysper and the design was very elegant to understand it quickly!

I don't know how to start with the contribution, but I observed a JIRA Item
- https://issues.apache.org/jira/browse/VYSPER-14 which I thought I will
pick up as my first task.

If I am not wrong, I couldn't see a configuration framework for Vysper
so I thought of the below Idea at the top of my head.

1. Identify the components that should be configurable and make them
implement an interface like "Configurable" which allows the component to
react to any configuration changes

2. All configurable Components should register with a ConfigurationManager
to receive configuration changes

3. ConfigurationManager is like a dispatcher which gets configuration change
signals from external sources[a] and transfers these signals to the
Configurable Interfaces

[a] I want to have multiple implementations of external sources through
which Vysper can be configured like for example, JMX MBean and Pure Java
Class which can read a configuration file and send configuration signals to
the ConfigurationManager which in-turn passes it to the Configurable
Components
Please advice me if any other source of configuration is required? like a
REST service?

Note: another option I could think of is make the configurable parameters of
each component to be class level members with an @Config annotation and
allow the ConfigurationManager to make use of this annotation to configure
the components.

Please provide me your thoughts and point me to some other tasks to start
with.

Thanks,
John

Reply via email to