[rabbitmq-discuss] Using listeners in json rpc server/client
stammailbox at gmail.com
Wed Mar 30 10:38:12 BST 2011
Yes . That's indeed a great option.
But it still raises questions I dont understand.
usually I do the two rows
channel.queueDeclare( [emptyStringForQueuename], bool,bool,bool... );
1. how does the channel know which queue to bind. what if it has two queues
with random name?
2. How will I add a new binding to a random named queue?
On Wed, Mar 30, 2011 at 9:07 AM, Steven Taylor <taylste at gmail.com> wrote:
> "You should name queues in a way that makes sense in your application. If
> queues are transient or the name doesn't matter then you can have the broker
> assign random names by supplying an empty string for the queue name."
> neat. Didn't know about that. Perhaps place it in a "random" exchange so
> as not to polute the routing key namespace.
> On 29 March 2011 15:50, Emile Joubert <emile at rabbitmq.com> wrote:
>> On 29/03/11 14:32, mysurf mail wrote:
>> 1. Is that design good? In places there used to be listeners
>>> transport for subscribing to data I will leave the jsonrpc solution
>>> and the listeners?
>> In a heterogeneous environment different components can communicate with
>> each other via a broker, regardless of their address. If that is your design
>> then it's good.
>> 2. what is the reccomended way to choose a name for the queue for
>>> each client
>> You should name queues in a way that makes sense in your application. If
>> queues are transient or the name doesn't matter then you can have the broker
>> assign random names by supplying an empty string for the queue name.
>> 3. When a client dies sudddenly (unexpected ) who will close his
>>> queue ?
>> You can set the queue to be auto-delete. When the last consumer
>> disconnects the queue will then be deleted automatically.
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss