How do OTHER Apache projects manage keyfiles and encryption bits and bobs? We're not the first, I'm sure.
Also, at Apache there seems to be a strong tradition of XML style config files -- even the style of the original httpd.conf file. Let's keep with the Apache culture. We should look at hot Tomcat and HTTPD and the Directory Project manage client and server SSL settings...... who ever is interested in coding this should #include one of those. John On 26/01/07, Colin Crist <[EMAIL PROTECTED]> wrote:
> > > > A couple of quick questions... > > > > 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 :-) Right > now, this would mean SSL, but it could mean other options > down the road. It should still be possible to get the client > running without a config file. Applications, especailly in house ones, have enough configuration files as it is without requiring them to have yet another one for a messaging product. I personally try and get all my configuration into an RDBMS (if I've got one already) for example and avoid files but that does not work for all. I certainly don't mind files for server side config but the client is part of a bigger picture the less you dictate deployment to the user the better. What particular bit of SSL needs reference to a file? Can I not also just use strings as well in the ConnectionFactory so you get files and other sources of config? Files are fine for som3, but its good to give options for others. Finally, if I bind a connection factory into JNDI then files don't work. Regards, Colin.
