Jason Walton

No, we don't do anything that fancy. `ampq-connection-manager` only connects to one of the nodes in the cluster at a time. If the connection dies, it cycles to the next...

That's an interesting idea. You could do this by supplying some function that evicts old messages from `_messages` when it gets too full?

If you have a PR that adds it in a clean way, I'd certainly merge it.

@terrasoff Try watching for `connect` and `closed` events from `amqp` instead of from the channel. @elizatlawy Calling `connection.close()` will close the connection - no further reconnect attempts will be made,...

Oh, but there should be connect/close events for the channel too...

`publish()` returns a promise which will resolve when the message is sent, so if you could do something like: ```ts const promises = []; promises.push(chan.publish(...)); promises.push(chan.publish(...)); promises.push(chan.publish(...)); // Wait until...

There's a call to `assertQueue` in the example you posted: ```js const channelWrapper = amqpConnection.createChannel({ json: true, setup(channel) { return channel.assertQueue('', { exclusive: true }); //

Oh, you're asking about replyTo... Sorry, just a sec. :)

The trick here is, we want to pass some information out of the `setup()` function and make it available to the rest of our program. I just pushed a new...

This is a problem you could theoretically have at any time; at startup, q is undefined because sendMessage is getting called before the channel is up, but later on if...