[rabbitmq-discuss] Comet interface

Alexis Richardson alexis.richardson at gmail.com
Sat Jul 4 13:10:13 BST 2009


I am going to jump in and try to answer your questions though please
bear in mind that I am far from intimate with some of the engineering

On Fri, Jul 3, 2009 at 12:06 PM, Ben Browitt<ben.browitt at gmail.com> wrote:
> Hi,
> I want to write a Comet web interface to RabbitMQ in Erlang.


> This interface will be responsible for authenticating users, managing
> sessions and routing messages.

Interesting.  How would auth work?

> For each logged-in user the interface will create a process that will route
> messages from the client to RabbitMQ,
> send messages from RabbitMQ to the client when possible and queue them in
> its mailbox when it's not.
> The reason for the queue is that in some implementations of Comet the client
> is not available 100% of the time.


> I wonder what is the best approach to communicate with RabbitMQ considering
> that the interface is in Erlang.
> One possibility is that each process will be an instance of the RabbitMQ
> client
> and the other option is that there will be one central process that will act
> as a bridge.
> I've noticed the http example

Before proceeding I would strongly recommend you dig into the existing
HTTP server and client example.  There may be duplication between
those and what you propose.  Indeed, if you could evaluate what we
have done and propose or write improvements, that could be very

>  .... and the STOMP adapter but read on several
> places that they don't work with every release
> probably because RabbitMQ is a moving target and is in active development (a
> good thing).

Yes, the release process for clients lags that for the broker at the
moment, partly because the whole team is very busy, and partly because
we are adding new features to the broker which, as Matthias says, are
of 'beta' status on initial release.

Other approaches you may wish to check out -

1. Use Orbited (open source) or Kaazing
2. Use RabbitHub:

> Do the http example and the STOMP adapter use one of the approaches I
> mentioned above?

Yes, I think there may well be similarities.  Take a look at the code.
 Maybe Tony will be tempted to comment over the weekend but please
note that the weather in London is currently pretty good ;-)

> Is the Erlang client stable?

It could benefit from review.  Please see the discussions between Jack
Moffitt and the team here, a few weeks ago.



> Thanks
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list