Michael Bridgen

Sorry, I have not had time to maintain this project for some time now. I don't mind if you wish to fork it or publish your own package.

Hi! Yes there's no particular reason it can't be updated, just me being busy. I ought to take a look at the other outstanding PRs and issues too!

RabbitMQ in general can be used as an "engine" in the terms of the discussion you point at, and rabbit.js may thereby be suitable as a convenient way of using...

That .. looks fine and works fine for me. Odd indeed. What versions of Node.JS and rabbit.js are you using?

Ah I see, you created the queue with a dead-letter exchange already (through the management UI perhaps?), then because rabbit.js doesn't know this and can't be told, it falls over....

I have pushed a change to master which lets you tell a socket not to try and create objects when connecting; this means you can use exchanges and queues created...

> It appears that this flexibility exists in Ruby's RabbitMQ lib, so I'm not sure regarding the reason for the handicap. This flexibility also exists in https://github.com/squaremo/amqp.node. Calling it a...

That sentence is supposed to indicate that the technique in the ordering example can also be used for worker sockets. Would it be better to say, > It is important...

rabbit.js is fairly portable code in itself (although, inevitably, written in callback/promises style); however, since it relies on amqp.node (aka amqplib), I don't think it's usable outside a Node.JS environment.

> (And sorry to squaremo if this feels disrespectful to have this discussion on a rabbit.js issue.) Yeah that is a bit cheeky, but since you had the grace to...