Perhaps you should look at the ACL (access control list) capability of
the broker. This allows you to restrict access to resources (i.e.
queues) based on the authentication identity of the client.
-Ted
ffrenchm wrote:
I have read this in the AMQP spec too and this is an interesting point. I've
the impression this is a something for example which could be improve in the
AMQP specification. I mean for example a useful functionality about exclusive
queue would to define queue with durable exclusivity and linked to a specific
client_id for example... I've the impression that this could not be achieve
with AMQP currently... but maybe it's not so useful as I think :)
++
I think this is the relevant text from the AMQP specification (emphasis
mine):
If the server receives a declare, bind, consume or get request for a
queue that has been declared as exclusive by an _*existing client
session*_, it MUST raise an exception.
This means that a queue is exclusive only as long as the client session
that declared it remains open. Once the session closes, the exclusive
ownership of the queue is released.
This is why the --exclusive switch on qpid-config would be meaningless
and why exclusivity cannot be durable.
-Ted
ffrenchm wrote:
Hello Ted,
my mistake comes in fact from my experience in other queuers where I can set a
durable exclusive parameter. What does mean this parameter ? It's mean that in
ANY case the queue will be exclusive even if the client do not open an
exclusive session... Thanks QMAN I see this parameter exists for the queue. I
think you should be able to use it as durable parameter. What do you think
about it ?
++
See my comment on QPID-1758. It's not meaningful to create an exclusive
queue with qpid-config because that queue will be exclusive to the
session created by qpid-config.
My understanding is that a queue is declared 'exclusive' by the client
that wants to use it. Once the session closes, the queue is available
for other sessions but the exclusive attribute no longer holds unless
it's re-declared.
-Ted
