<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<pre>
<b>Matthias Radestock</b> <a
href="mailto:rabbitmq-discuss%40lists.rabbitmq.com?Subject=%5Brabbitmq-discuss%5D%20whether%20the%20weather%20is%20right.&In-Reply-To=4442b4720811080736h7e2a5d81p41321f644e7ab454%40mail.gmail.com"
title="[rabbitmq-discuss] whether the weather is right."></a><i>wrote:</i><i></i>
> Peter Silva wrote:
> ><i> To me, unicast/direct, multi-cast/topic, broadcast/fanout data
</i>> ><i> distribution has nothing to do with how the data arrived at the
</i>> ><i> switch/broker/exchange. Neither producer, nor consumer should have
</i>> ><i> anything to say about that.
</i>>
> Then who does? Some administrator? If so, just write a small AMQP client
> app that creates the exchanges, queues and bindings, and run that as the
> administrator. Producer then will just need to know the name of the
> exchange, and consumers the name of their queue.
Will the consumers be able to change the bindings when they connect?
</pre>
</body>
</html>