[rabbitmq-discuss] RabbitMQ+STOMP: how to trigger events upon connect/subscribe to stomp destinations?

Marek Majkowski majek04 at gmail.com
Thu Jun 17 12:47:32 BST 2010


On Sun, Jun 13, 2010 at 13:14, Willi Richert <w.richert at gmx.net> wrote:
> I am using RabbitMQ+STOMP as a MorbidQ replacement in the Orbited orbit.
> With MorbidQ I had the possibility to use a custom RestQ listener
> (http://www.morbidq.com/trac/wiki/RestQ ) for doing auth and other stuff. As
> auth is perfectly handled by RabbitMQ I am looking now for ways to handle
> the "other stuff":

Just out of interest, can I ask is there any particular reason why
might be better for you than MorbidQ?

> When a user surfs on some web page, it connects to Orbited via stomp and
> subscribes to a secret destination where it listens for updates. At the
> point when the browser subscribes, my RestQ listener signaled all the other
> browsers visiting the same page that a new user arrived (via STOMP messges).

What I understand:

[browser] ---(http)---> [RestQ--->MorbidQ] ---(stomp)---> [orbited]
---(http)---> [browsers]

> What is the preferred way for this in RabbitMQ. Is there some similar
> restful service?

We do have an attempt to create some sort of restful interface for rabbitmq
but it's experimental and _not_ supported.

On the other hand I can't see a reason why you just won't publish a
stomp message
from your normal web server. Something like:

[browser] ---(http)---> [your-web-server] ---(stomp)---> [orbited]
---(http)---> [browsers]

   Marek Majkowski

More information about the rabbitmq-discuss mailing list