<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Thanks, that was exactly what I was looking for. I should have seen that initially. One followup question, I was thinking that I could have one exchange that distributed to multiple exchanges before distributing to queues. This may allow me to hang multiple queues off of some exchanges thereby maybe reducing the initial distribution algorithm's search path. Is there anything to gain by this performance wise? Are exchanges lighter than queues in terms of routing (I'd wind up having the same number of final destination queues).<div><br></div><div>Thanks,</div><div>Alex<br><br><div><div id="SkyDrivePlaceholder"></div>> Date: Thu, 20 Sep 2012 11:52:49 +0100<br>> From: emile@rabbitmq.com<br>> To: rabbitmq-discuss@lists.rabbitmq.com<br>> CC: alex.gadea@apptik.com<br>> Subject: Re: [rabbitmq-discuss] How to handle distribution of message to either 1 OR many topics<br>> <br>> Hi Alex,<br>> <br>> On 20/09/12 03:23, Alex Gadea wrote:<br>> > message 1: audit.webhook<br>> > message 2: webhook<br>> > message 3: email.audit.webhook.s3<br>> <br>> You should take a look at section 3.1.3.3 (The Topic Exchange Type) in<br>> the AMQP 0-9-1 specification which explains this:<br>> http://www.rabbitmq.com/protocol.html<br>> <br>> The 5th tutorial also has some useful information:<br>> http://www.rabbitmq.com/tutorials/tutorial-five-python.html<br>> <br>> #.webhook.# should capture all 3 messages.<br>> <br>> If the publisher known exactly where a message should be routed then you<br>> might want to consider Sender-selected distribution. However if you have<br>> 100s of destination queues then this is probably not relevant:<br>> http://www.rabbitmq.com/sender-selected.html<br>> <br>> <br>> -Emile<br>> <br></div></div> </div></body>
</html>