I don't understand why we have two different styles for declaring queue
parameters.
Some have explicit parameters that are used in session.queueDeclare:
session.queueDeclare(arg::queue=myQueue,
arg::exclusive=true,
arg::autoDelete=true);
We have defined arg:queue, arg::durable, arg::autoDelete, arg:exclusive,
and arg:alternateExchange.
How are these different from QueueSizePolicy or QueueOrderingPolicy,
which take a second approach (specifying values for a property)?
QueueOptions qo;
qo.setOrdering(LVQ);
session.queueDeclare(arg::queue=queue, arg::arguments=qo);
And how are these different from persisting the last node or queue
events, which take a third approach (specifying properties for the queue)?
QueueOptions qo;
qo.clearPersistLastNode();
session.queueDeclare(arg::queue=queue, arg::durable=true,
arg::arguments=qo);
QueueOptions options;
options.enableQueueEvents(false);
session.queueDeclare(arg::queue="my-queue", arg::arguments=options);
Can we pick just one way of doing this?
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
