[rabbitmq-discuss] reg rabbithub how to

Michael Bridgen mikeb at rabbitmq.com
Wed Jul 21 10:44:55 BST 2010

Hi Akhil,

> Yup, I can see it.
> I meant I needed any HTTP way of accessing queues and exchanges.
> Is there anything that I should be aware of while using it?

Depends what you mean by "accessing".  For instance, PuSH, and thereby 
RabbitHub, doesn't have a discovery mechanism.  It's just the messaging.

One thing to be aware of is that RabbitHub treats PuSH as a symmetric 
messaging protocol -- on one side it accepts subscriptions from 
downstream (the "subscription" interface, e.g., 
http://localhost:55672/rabbithub/subscription/q/myqueue), and on the 
other it accepts messages from upstream (the "endpoint" interface, e.g., 

It's also content-agnostic, and doesn't try to do any of the XML/Atom 
processing implied in the PuSH specification.

Each exchange and queue in RabbitHub is exposed as its own PuSH hub, 
with the topics being AMQP routing keys.  You can also create and delete 
exchanges and queues using PUT and DELETE.


> Thank you
> Akhil Kodali
> On Wed, Jul 21, 2010 at 2:43 PM, Michael Bridgen <mikeb at rabbitmq.com 
> <mailto:mikeb at rabbitmq.com>> wrote:
>         I compiled and installed rabbithub as a rabbitmq plugin from github.
>         What do I do next? I mean how do I begin using it.
>     The rabbitmqctl status output you posted suggests you got it running
>     OK, but for the record:  If you've successfully compiled it, you can
>     either symlink in into rabbitmq-server/plugins/ or drop the
>     rabbithub.ez in the same place.  RabbitMQ should then tell you the
>     RabbitHub has started up during boot.
>     It will be running under control of RabbitMochiweb at
>     http://localhost:55672/rabbithub/
>     In general you'll need to address endpoints, e.g.,
>     http://localhost:55672/rabbithub/endpoint/x/amq.direct
>         I am trying to use it primarily as a REST way for consuming from
>         queues.
>     RabbitHub implements PubSubHubbub (a.k.a., PuSH), which isn't
>     RESTful (and shouldn't be).  However, it *is* a fairly idiomatic use
>     of HTTP.
>     Hope this helps; have fun!
>     Michael
> ------------------------------------------------------------------------
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list