mikeb at rabbitmq.com
Wed Feb 16 23:15:28 GMT 2011
> RabbitMQ. Nodejs, however is server side. Am I maybe misunderstanding
rabbit.js is indeed written for node.js, but it enables the Socket.IO
library on clients to speak to RabbitMQ, in effect. However it is
toyware right now, and doesn't support topic routing.
There's also rabbit-socks, which is being actively worked on and is
intended to support STOMP-over-websockets(/Socket.IO) among other
things, in the not-too-distant future. That's probably a better fit if
you can wait, Jeff.
Oh and there's rabbitmq-jsonrpc-channel, which is available now but not
being actively worked on, except to keep it up-to-date with RabbitMQ API
> On Wed, Feb 16, 2011 at 2:47 PM, Alexis Richardson<alexis at rabbitmq.com> wrote:
>> I shan't dare to recommend something but you might want to consider:
>> I am not sure if this addresses your needs. If it does not then let
>> us know, since there are other options.
>> On Wed, Feb 16, 2011 at 5:14 AM, Jeff Hinrichs<jeffh at delasco.com> wrote:
>>> Looking for recommendations for js libraries to communicate with RabbitMQ.
>>> expected usage patterns: Topic based exchanges, mostly consuming, some rpc
>>> desirable attributes: fewer dependencies are a plus, no problems
>>> co-existing with jquery, actively developed, good community/docs
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss