I did a clean install of Python with the 0.8 module and it is working
as expected on both Windows and Linux, so I was clearly
troubleshooting the wrong things. I previously had the 0.6 version
installed before I added the 0.8 version. Thanks for your responses
and suggestions!
Greg
On Tue, Feb
On 02/14/2011 09:45 PM, Gregory Bayard wrote:
Hi Gordon,
I was originally working with 0.6 and the double-quoting was a quick
attempt to find some problem with my exchange and queue specification.
When I updated my addressing string for Qpid 0.8, I still get the
same result. The message is pi
On 02/14/2011 04:45 PM, Gregory Bayard wrote:
Hi Gordon,
I was originally working with 0.6 and the double-quoting was a quick
attempt to find some problem with my exchange and queue specification.
When I updated my addressing string for Qpid 0.8, I still get the
same result. The message is pi
Hi Gordon,
I was originally working with 0.6 and the double-quoting was a quick
attempt to find some problem with my exchange and queue specification.
When I updated my addressing string for Qpid 0.8, I still get the
same result. The message is picked up by topic listeners listening to
the maste
On 02/11/2011 04:37 PM, Gregory Bayard wrote:
Hello,
I am using the Apache QPID 0.8 release. I have a C++ QPID application
using the request/response model which I would like to build a Python
client for. The C++ listens for a response on a queue called
'masterserver.summary.queue' bound to a c
Hello,
I am using the Apache QPID 0.8 release. I have a C++ QPID application
using the request/response model which I would like to build a Python
client for. The C++ listens for a response on a queue called
'masterserver.summary.queue' bound to a custom direct exchange it
declared, 'masterserver