Gordon Sim wrote:
Rafael Schloming wrote:
Gordon Sim wrote:
I think you might actually want to control that explicitly, e.g.
have something like this:
queuex.MyQueue = {create-on-send=true, create-on-receive=false, ...}
Why could you not do this on a 'destinationx'? That would seem much
neater to me.
I could see that you might want to put the auto-create flag(s) on the
destinations themselves, but I would think the queue properties should
only be specified once since they may be reference from multiple
destinations
If I have only one destination defined for that queue and want it to be
auto-created can I put the queue options in the definition of that
destination?
I would certainly prefer that in most cases. I can understand the desire
for a mechanism to reference options defined elsewhere I'm just not sure
its worth it though.
I.e. should the address+options syntax (which is the part that would be
reused across languages and in the createQueue()/createTopic() method
calls) support auto-created queues?
I was thinking the format for specifying queue properties would be
standard across languages regardless of whether the queue declaration is
separate or nested.
If you're talking about something like this:
dest.D = MyQueue; {auto-create=true, queue-definition={durable=true,
...}, ...}
or even this:
dest.D = MyQueue; {auto-create={durable=true, ...}, ...}
then I don't really care whether the queue definition is separate or not.
I would prefer to avoid something like this though where the queue
options are mixed together with the consumer/producer options:
dest.D = MyQueue; {exclusive=true, prefetch=100, auto-delete=true, ...}
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
