Hi Kevin,
I've already attached a patch to the JIRA for the Java broker changes.
Once we
> can agree on one or the other I'll be able to finish the Java client
work.
I think a (simple!) XML configuration file will do the trick and fully
support that.
Given that we cannot control the context in which the client library is
deployed, I think we need to be flexible in the way in which these
configuration options can be set. That is I think that it should be
possible to configure the library by passing in a
commons.Configurationobject. In that sense for the (Java) client I
think the decision over XML
vs YAML vs Properties file etc may be something of a red-herring. However I
am +1 for using XML as the default and as the basis for a common
configuration style between clients / brokers of all languages.
A couple of quick questions...
With the Java Client changes, will the client now always require a
configuration file? [ I hope not :-) ] ... And at what level are you
planning to make these options configurable (application instance or
connection being the two most obvious).
Cheers,
Rob
