On Mon, Sep 09, 2013 at 02:53:20PM -0400, Rajesh Khan wrote:
> While going through the manual I came across the following
>
> Create, Delete, and Assert Policies
> The create, delete, and assert policies specify who should perfom the
> associated action:
>
> • always: the action is performed by any messaging client
> • sender: the action is only performed by a sender
> • receiver: the action is only performed by a receiver
> • never: the action is never performed (this is the default)
>
> So I am thinking that If I create the sender as such
>
> std::string sender_string = std::string("amq.topic/") + queue_name
> +";{create:always, delete:sender, node:{type:topic}}";
>
> The following characteristics would be exhibited (Please correct me if I am
> wrong)
>
> 1-Once the sender application stops due to whatever reason the exchange
> gets removed and all the receivers would get an exception ?The best thing to do is to tinker and test out the scenario using the spout and drain tools. :) -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgpHKyqm79gU0.pgp
Description: PGP signature
