Robert Greig wrote:
On 23/01/07, Kevin Smith <[EMAIL PROTECTED]> wrote:
2) Does this config need to be interchangeable with the C++ broker?
I'm not sure any of our config is interchangable with the C++ broker.
My understanding, having only started looking into the C++ broker a
couple of days ago (coincidentally, to start implementing security and
bring it up to par with the Java broker), is that there's no actual
configuration files, all options are passed on the command line.
I understand and respect that there's been an effort to keep
configuration to an absolute minimum on the C++ broker, so maybe we can
follow that lead and keep SSL-related config as command line
parameters... on the other hand, if there's a large number of
configurable options, it may become too complicated to do it all from
the command line and I start seeing the need for a config file
(especially if there are no universally useful defaults). I don't feel
strongly either way, I'll defer this to the people who have worked on
the C++ broker more extensively.
One option that would enable reuse of the Java xml config while still
keeping the command line oriented nature of the C++ broker would be to
"wrap" the C++ broker binary with a script that would read the file and
pass the appropriate values as command line parameters. But that would
only push the issue onto a separate layer, not eliminate it.
Nuno
