[rabbitmq-discuss] Message routing

[Martin Sustrik]

I would probably implement this in a following way:

1. I would separate messages into different exchanges. Each exchange 
would correspond to a service customer can buy. The producer application 
creates the exchanges on the startup. When client buys a service, he 
gets access to the corresponding exchange.

2. Client application creates its own queue and binds to desired 
exchange (of course only if the service was bought already, otherwise it 
should get access error) with any routing criteria. These criteria can 
be changed afterwards using Queue.Bind and Queue.Unbind commands.

Martin

John Watson wrote:
> Martin wrote
>> This is the case because of the zero-config feature of AMQP. I.e. 
>> install and run the software on 1000 boxes of your server farm without
> any extra work.
> 
> Well, to me, this seems to be deferring the administration to some other
> kind of process. Suppose that you wish to publish messages to 1000
> different customers, each with their own box.  Let's say each customer
> has his own routing rules, and that these rules are quite complex, and
> change from time to time as and when business requirements change and
> cause different subsets of the available messages to be received. 
> 
> Suppose also that you want to control the message routing yourself (in
> response, say to a customer buying a new service from you), and you want
> absolute control over the security of your own box.  What must you do?
> 
> John
> 
> *************************************************************
> Satellite Information Services Limited Registered Office: 
> 17 Corsham Street London N1 6DR, Company No. 4243307
> 
> The information in this e-mail (which includes any files
> transmitted with it) is confidential and is intended for the
> addressee only. Unauthorised recipients are required to
> maintain confidentiality.  If you have received this e-mail
> in error please notify the sender immediately, destroy any
> copies and delete it from your computer system. 
> *************************************************************
>