[rabbitmq-discuss] Administering Rabbit exchanges and queues
0x6e6562 at gmail.com
Fri Jan 11 13:47:25 GMT 2008
Thanks for picking that one Matthias.
John, please find my comments inline.
On 11 Jan 2008, at 13:44, Matthias Radestock wrote:
> I suspect you meant to send this to the discuss list rather than amq at lshift.net
> Ben Hood wrote:
>> On 11 Jan 2008, at 12:12, John Watson wrote:
>>> I'll certainly do that. But I think Ben was saying that his
>>> approach is
>>> currently limited to what's exposed in rabbit_access_control so it
>>> me nothing new as far as I can tell.
>> The approach is only limited to rabbit_access_control by virtue of
>> the fact that that's only rabbit module I've tested against.
>> Essentially it is a generalized RPC over AMQP handling mechanism
>> that on the server side takes a concrete Erlang module as a
>> parameter to a handler instance. So presenting a further module via
>> this mechanism is trivial:
>> Client ---> Java Interface ---> Dynamic Proxy --> Wire --> Queue --
>> > RPC Handler --> Erlang module
>> The only thing you have to add is
>> 1. The business module whose exported functions you wish to invoke
>> 2. A Java interface definition of those functions.
>> Everything else is generic.
>>> If you want requirements to add to
>>> 0-11 then I'd say that the three most important components seem to
>>> the exchange, queue and binding and these should be fully
>>> in order to allow for scripting, GUI tools etc. to manipulate them
>> It sounds like you might to start with a wish list of functions you
>> would like to be able to invoke, rather than exposing the kitchen
>> sink unnecessarily.
More information about the rabbitmq-discuss