[rabbitmq-discuss] Administering Rabbit exchanges and queues

[John Watson]

Hi, Alex

When you say
> what would you expect to see API-wise?

I'm not completely sure: Ultimately I'm interested in setting up a
network of servers with a reasonably static topology that manage
point-to-point messaging, with store-and-forward in case of network
outages and with reasonably static message routing. I'd like to be able
to set this up in some declarative manner. So I suppose I'm mostly
interested in such attributes as exchange: type, durability, bindings:
routing keys, also access rights to the various components and
authentication of the connections between servers.

I'm very conscious that I seem to be talking at cross-purposes here -
I've been grappling with the problems of easing the administration
burden for our MQ network for the last couple of years and it's
colouring my approach to Rabbit.  I certainly didn't intend you to
expose the whole kitchen sink......

John

-----Original Message-----
From: alexis.richardson at gmail.com [mailto:alexis.richardson at gmail.com]
On Behalf Of Alexis Richardson
Sent: 11 January 2008 13:32
To: John Watson
Cc: Matthias Radestock; rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] Administering Rabbit exchanges and
queues

John

On Jan 11, 2008 12:12 PM, John Watson <JWatson at sis.tv> wrote:
>
>  If you want requirements to add to
> 0-11 then I'd say that the three most important components seem to be
> the exchange, queue and binding and these should be fully
administrable
> in order to allow for scripting, GUI tools etc. to manipulate them
> fully.

Thank-you.  Towards full administrability, other than obtaining a list
of live queues (.., exchanges, bindings), what would you expect to see
API-wise?

alexis



-- 
Alexis Richardson
+44 20 7617 7339 (UK)
+44 77 9865 2911 (cell)
+1 650 206 2517 (US)

*************************************************************
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. 
*************************************************************