On 08/26/2011 12:38 PM, tomas.sol...@deutsche-boerse.com wrote:
Ok than.
So is this an expected behaviour or should I raise a JIRA.
Raise a JIRA, it would be much better if the clients behaved the same
and did not require different ACL rules.
Ok than.
So is this an expected behaviour or should I raise a JIRA.
Thanks,
Tomas
Gordon Sim
26/08/2011 13:14
Please respond to
users@qpid.apache.org
To
users@qpid.apache.org
cc
Subject
Re: C++ and Python client diferences
On 08/26/2011 11:24 AM, tomas.sol...@deutsche-boerse.com
On 08/26/2011 11:24 AM, tomas.sol...@deutsche-boerse.com wrote:
Hi Gordon,
Thank you for your reply.
But there is still one thing I do not understand.
I have set the log level to trace+ on my broker and here is what I got
from the log when I have used the same same addres for python as well as
ACL rules and change the adress as
stated in my previous email.
Thanks and regards,
Tomas
Gordon Sim
25/08/2011 14:27
Please respond to
users@qpid.apache.org
To
users@qpid.apache.org
cc
Subject
Re: C++ and Python client diferences
On 08/25/2011 09:57 AM, tomas.sol...@deutsche-
On 08/25/2011 09:57 AM, tomas.sol...@deutsche-boerse.com wrote:
Hi,
I am using qpid 13.0 API (from apache SVN) to build my C++ client and I
have came across this interesting difference when compared to Python
client.
So for Python I am using this address:
response/response.QPID_CLIENT.response
