On 23 April 2016 at 19:43, Robbie Gemmell wrote:
> There were 11 binding +1 votes, and no other votes received. The vote
> has passed.
>
> Robbie
This has now been completed. The site content is on the 'asf-site'
branch in the new qpid-site repo at
On 04/28/2016 05:16 AM, Alexandre Trufanow wrote:
Hi guys,
I'm taking over Adel's work on porting the dispatcher, I have a few
additional comments to make.
*@Chuck,*
I took a look at Qpid C++ broker model but the main issue is it is
C++
oriented whereas the dispatcher is mainly C. I tried to
If there any problems viewing ACL rule or log,it maybe connected to nabble
formatting.
You can view original message at
http://qpid.2158936.n2.nabble.com/ACL-Java-Broker-6-0-2-AMQP-1-0-td7642793.html
--
View this message in context:
Hi,
I am testing Qpid Java Broker 6.0.2. I am struggling with setting ACL
rights for AMQP 1.0 (qpid-jms-client 0.9.0) client.
For AMQP 0-10 (qpid-client 6.0.2) ACL rights are working as expected.
When I use same ACL rights for AMQP 1.0 as in AMQP 0-10, looks like client
is not
Hi guys,
I'm taking over Adel's work on porting the dispatcher, I have a few
additional comments to make.
>>> *@Chuck,*
>>> I took a look at Qpid C++ broker model but the main issue is it is
>>> C++
>>> oriented whereas the dispatcher is mainly C. I tried to switch the
>>> compiler
>>> of Visual
Thanks a lot for you answers Ted. I'm looking through the configurations in
the tests.
>> * When messages are sent to a dispatcher, I would expect to be able to
>> retrieve them directly from the brokers. However, It is necessary to read
>> the messages from a dispatcher most of the time, as