Hi Martin,
I will not explain the advanced configuration section in my Java Broker
README in that case. I will just limit to two lines explaining its intent.
Also, i did figure out the ${conf} is a directory. But there is no
subdirectory named virtualhosts as yet, which seem to be answered in your
reply.
Regards,
Senaka
On Tue, May 20, 2008 at 5:53 PM, Martin Ritchie <[EMAIL PROTECTED]> wrote:
> 2008/5/20 Senaka Fernando <[EMAIL PROTECTED]>:
> > Hi again,
> >
> > Thanks for the valuable guidelines. I'm almost done writing the README
> for
> > the config.xml. However, I'm yet to understand the,
> >
> > <advanced>
> > <filterchain enableExecutorPool="true"/>
> > <enablePooledAllocator>false</enablePooledAllocator>
> > <enableDirectBuffers>false</enableDirectBuffers>
> > <framesize>65535</framesize>
> > <compressBufferOnQueue>false</compressBufferOnQueue>
> > <enableJMSXUserID>false</enableJMSXUserID>
> > </advanced>
> >
> > section. As it seems it is a bit advanced to figure out. :)...
> >
> > Also, there are two elements configuring virtualhosts. I would like to
> know
> > how this works out. And, I would also like to understand what
> > <directory>${conf}/virtualhosts</directory> actually points to.
>
> This one has an outstanding bug. ${conf} is not as you would expect
> 'the value configured at the start of the config.xml' it is the
> directory that contains the config.xml file.
>
> The two virtualhost elements are simply combined. And should
> eventually be split out. so we have:
> config.xml
> virtualhosts/localhost.xml
> virtualhosts/test.xml
> ...
>
> I'd also like to see a lot of items removed from config.xml the whole
> advanced section for example. There is no need for a user to tweak
> these values and more chance they will break something. The items that
> they may want JMSXUserID and BufferCompression(perhaps not) could be
> factored in elsewhere. Perhaps per virtualhost or even per queue.
>
> Cheers
> Martin
>
>
> > Regards,
> > Senaka
> >
> > On Tue, May 20, 2008 at 5:37 PM, Robert Greig <[EMAIL PROTECTED]>
> > wrote:
> >
> >> 2008/5/20 Senaka Fernando <[EMAIL PROTECTED]>:
> >> > Hi Robert,
> >> >
> >> > Thanks for the reply. I would like to know whether
> >> > <transport>nio</transport> is deprecated and, the meanings of
> >>
> >> Well, at one time we had another (non-nio) transport but it wasn't any
> >> faster so it probably got removed. At the moment it's the only option
> >> but that does not preclude a new one in future of course,
> >>
> >> > 1. security/principal-databases/principal-database/class
> >> > 2. security/access/class
> >>
> >> Take a look at:
> >> http://cwiki.apache.org/qpid/qpid-design-authentication.html which I
> >> think covers this.
> >>
> >> RG
> >>
> >
>
>
>
> --
> Martin Ritchie
>
