Hi Robert, Some answers inline below.
----- "Robert Greig" <robert.j.gr...@gmail.com> wrote: > I have been using the C++ broker for the first time when doing some > testing of the WCF client. When doing this, I have made some > observations as a "new user": > > 1) the broker's default output logging level is nothing. If you start > it up, it gives no indication that it is doing anything at all. Is > this deliberate? I think it should really be INFO level, or at least > some level that enables the user to see that it is listening on a > port > without running netstat. Yes it is deliberate. Default is silent. You can run it with -t or --trace to get some logging output. qpidd also uses it's own queuing mechanism for doing management logging. Info regarding the broker can be viewed using qpid-tool command-line tool or by using the management console, though sometimes it's nice to turn on -t for development work. > > 2) the broker does not complain when you give it an option that it > doesn't understand. For example: > > qpidbroker /eatmoremincepies > > doesn't yield any error or usage string. (After point 1, the curious > user may try to get help with the /help argument). Nice catch! Nice that it doesn't crash I suppose but it should respond the same way it does when you give it --eatmorenicepies. Perhaps '--' is still the default for parameters on windows? '/' is certainly more windows-like. Probably should log a bug on this one - at least for the ignoring of /eatmoremincepies though perhaps there is a case for changing the default parameter prefix to '/'. Worth debating. > > 3) How do you configure authentication in the windows broker? The > info > I read in one of the files in the distro didn't seem to apply for > windows since it involved using a tool to create users. I had to > disable authentication to get my client to run. There are some ACL options you can see when you run qpidd --help. Best for the holidays, William > > RG
