Michael Bridgen
Michael Bridgen
> Any thoughts as to why this would not be a good idea? 'auto-delete' means the queue will be deleted once there are no consumers; for example, if you connect...
Hi there, thank you for bug report. It is reasonable to expect your code to work. The reason it's not -- I suspect (I'll investigate further) -- is that the...
I am thinking that a 'persistent' socket, either set in the constructor or by setsockopt, should declare its exchange to be durable. Does that break anything? (except backwards compatibility)
> Does it break backwards compatibility? In the sense that someone already using a "persistent" PUB or SUB socket will encounter breakages, since rabbit.js will try to re-declare the exchanges...
Which headers/properties? You might be better off using squaremo/amqp.node directly -- it's not much more complicated that rabbit.js.
> I'm not seeing anything in this repo that would allow me to authenticate a connection. The `createContext` procedure allows you to supply a connection URL, and this takes the...
This is not really encouraged, by design -- PUB/SUB sockets are meant to only collect messages while your application is running. You may find it easier to encode what you...
Is that because you are using it from another library?
Right. And those other applications need it to be durable, so e.g., bindings don't go away. I suppose it would make sense if a "persistent" PUBLISH socket declared its exchanges...
The constructor arguments tend to just set the default for that socket, so I guess it can be in both places.