On Tue, 2014-10-21 at 11:43 +0400, Michael Ivanov wrote:
> Greetings!
>
> I am new to qpid-proton, can somebody give me some pointers on how to get
> replies
> for the messages when working via qpidd broker? I tried to use
> msgr-{send/recv}
> examples from tests/tools, they seem to work fine when used without broker
> (I used primary queue address string amqp://~0.0.0.0/q1 and reply queue name
> "~").
> When I use a qpidd broker I use amqp://127.0.0.1/q1 to acces primary queue and
> I tried both "~" and "~/q1" as reply_to names. In both cases I have seen that
> replies were sent to some "amqp://xxxxx......xxxxxx" address (with or without
> q1 appended) but it looks like reply messages are lost, send program hangs
> forever waiting for reply.
>
> I tried using hardwired reply queue name (setting reply_to to
> "amqp://127.0.0.1/q1-reply")
> and this worked, but in this case I have to pre-create reply queue manually
> using qpid-config. Is there a way to create temporary (auto-delete) queues
> from proton library?
>
> Finally is there any way to read only messages with specified priority from
> input queue in proton C?
>
> I am currently using qpid-proton 0.7 with qpidd from qpid-cpp 0.30
>
> Best regards,
Two examples that might help:
The qpid dispatch project has a management client with a
proton.Messenger based request-response pattern in python:
http://svn.apache.org/repos/asf/qpid/dispatch/trunk/python/qpid_dispatch/management/client.py
The new proton tutorial (not on trunk yet I think but you can see it on
the branch below) has a request-response example that is based on the
proton engine rather than on Messenger. Long term I plan to use this
approach rather than Messenger for the dispatch management client.
http://svn.apache.org/repos/asf/qpid/proton/branches/examples/tutorial/sync_client.py
Note the tutorial code doesn't check correlation ID's, I'll fix that
shortly but you can just cut and paste the correlation ID code from the
Messenger based client.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
