[rabbitmq-discuss] Internal services (was Re: Queue info)
chime at mu.dk
Sun Sep 7 20:40:37 BST 2008
Sorry for the late reply.
As far as I remember, my primary concern was dependency on the
internals of Rabbit and also on Rabbit itself.
Using the erlang client would solve both problems.
On Jul 16, 2008, at 12:55 , Ben Hood wrote:
> On Wed, Jul 16, 2008 at 10:44 AM, Tony Garnock-Jones
> <tonyg at lshift.net> wrote:
>> Hi Michael,
>> Michael Arnoldus wrote:
>>> Speaking of which - if it should happen that I one late night are
>>> finding myself sorely missing working in erlang to the degree that
>>> like to experiment with this - do you have any docs or just
>>> pointers to
>>> how to receive and send AMQP from inside erlang? I guess using the
>>> erlang AMQP client to let the server talk to itself isn't exactly
>>> right approach ...
> Can you elaborate on why using the Erlang client to let the *server
> speak to itself* may the wrong approach?
> As Tony has pointed out in the previous post, you can use the internal
> rabbit API to send and receive messages, but this means that you tie
> yourself in the internals of Rabbit, which *may* change over time.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1912 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080907/0f769b03/attachment.bin
More information about the rabbitmq-discuss