[rabbitmq-discuss] Per-Connection Queue Creation and Deletion

[Michael Klishin]

On oct 3, 2013, at 6:43 p.m., Tiago Boldt Sousa <tiagoboldt at gmail.com> wrote:

> I'm not being able to either limit queue creation to exclusive,

This is not supported by access control.

> nor limit the topics a client can subscribe to.

Message distribution happens during routing, not consumption. You can limit
what exchanges and queues a user can use, see http://www.rabbitmq.com/access-control.html

> I could impose this constraint based on VHOSTS, but that would require the dynamic creation of VHOSTS and probably hundreds of them. 

Hundreds of vhosts is not a high number. While somewhat inconvenient, this may work
well in practice.

> Is this possible in RabbitMQ? Is there a better approach to it?

You can enforce exclusive queue creation in your application code. As far as topic
restrictions, you can create several users and limit their access only to particular
topic exchanges.

MK



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131003/abe73161/attachment.pgp>