Tomas Restrepo wrote:
Hi Kevin,
With the Java Client changes, will the client now always require a
configuration file? [ I hope not :-) ]
The client would only require a config file if you wanted to configure
options
which would require a config file :-)
I can't speak about the Java client per se since I don't know about how
people expect to use it. However, I'm collaborating a bit on the .NET client
and wondering a lot about some of the same issues you're talking about
(including the SSL support which hasn't been added yet).
Given this, I know how I'd like to use the .NET client for some stuff and
things like SSL should definitely be configurable from code without needing
an external configuration file, at least from in my very humble opinion. I
would think that at the very least, the option to enable SSL or not as well
as the client certificate should be easily exposed programmatically at the
time the connection to the broker is opened, and I was thinking that
exposing this in some way in the ConnectionInfo sounded like the a
reasonable approach.
It's OK for a broker to depend on explicit configuration, but a client
library is usually used in very different contexts, and at least in some of
those forcing external configuration is going to cause a lot of troubles.
Likewise, it's very OK to be able to use external configuration (an XML file
for example) as an *alternative* to the API, but shouldn't be the only way
to set options like this, I think.
+1. This is what I was thinking. The approach I took with the broker was to add
API to allow it to be configured and then added the logic in the config layer to
call the appropriate API with the values from the file.
I was going to do something very similar for the client.
Then again, it's just my opinion :)
Tomas Restrepo
[EMAIL PROTECTED]
http://www.winterdom.com/weblog/
