Robbie,
I was actually looking for an example of the following, which works in the
manner I was hoping for.
"const char* response_queue="#response_queue; {create: always delete: always,
receiver}"
So now when I close the receiver the queue goes away.
The documentation is definitely moving at a much slow pace than development.
The examples are good but it would help to have more inline comments.
As aside it would be interesting to find some development guidance of how to
move from the C++ Messaging API to Proton. I myself would like to be able to
see a side by side comparison of a simple sender and receiver "expressed" in
the C++ Messaging API and in C++Proton. Maybe I should start that as a
separate discussion item.
Paul
________________________________________
From: Robbie Gemmell [[email protected]]
Sent: Tuesday, April 05, 2016 4:39 AM
To: [email protected]
Subject: Re: Question: Temporary queues: set up and when do they go away?
Have you tried doing what the example does that Gordon linked to and I
described further yesterday?
Robbie
On 4 April 2016 at 16:54, Flores, Paul A. <[email protected]> wrote:
> As subject states.
>
>
>
> Unclear how use so of the Address options as they are described.
>
>
>
> How do I set up a temporary queue that goes away when the receiver is closed?
>
>
>
> I am using the following in my code to set up a response queue.
>
>
>
> What has me asking this question is that using qpid-cofig I can see that
> before I run my example applications there is only 1 non-durable queue. But
> well after my example applications finishes (receivers and senders are
> closed) I see 2 non-durable queues. Shouldn't the queue be deleted and not
> appear at all when I run qpidd-configure? What am I doing incorrectly?
>
>
>
> "const char* response_queue="#response_queue; {create: always, delete:
> always}"
>
>
>
> Thanks for your help it is appreciated!
>
>
>
> Paul
>
>
> ________________________________
>
> This communication (including any attachments) may contain information that
> is proprietary, confidential or exempt from disclosure. If you are not the
> intended recipient, please note that further dissemination, distribution, use
> or copying of this communication is strictly prohibited. Anyone who received
> this message in error should notify the sender immediately by telephone or by
> return email and delete it from his or her computer.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
________________________________
This communication (including any attachments) may contain information that is
proprietary, confidential or exempt from disclosure. If you are not the
intended recipient, please note that further dissemination, distribution, use
or copying of this communication is strictly prohibited. Anyone who received
this message in error should notify the sender immediately by telephone or by
return email and delete it from his or her computer.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
