You can find out about the exclusive banner and other queue properties into the guide on queues.
We have currently developed a fanout trade and a queue. Now we must inform the trade to deliver communications to your queue. That relationship between change and a queue is known as a binding.
To any extent further the logs trade will append communications to the queue.
You are able to record bindings that are existing, you guessed it,
Placing it completely
The producer program, which emits log communications, does not look much distinct from the past guide. Probably the most crucial modification is that we currently wish to publish communications to your logs exchange rather than the nameless one. We have to supply a routing_key whenever delivering, but its value is ignored for fanout exchanges.
We declared the exchange as you see, after establishing the connection. This task is essential as publishing to a exchange that is non-existing forbidden.
The communications would be lost if no queue is likely to the change yet, but that is ok for all of us; if no customer is listening yet we are able to properly discard the message.
We are done. If you’d like to conserve logs to a file, just available a type and console:Seguir leyendo