Subscriptions flow to all nodes in the network that support the stream in question. This is shown in Figure 5.
A broker consolidates all the subscriptions that are registered with it, whether from applications directly or from other brokers. In turn, it registers subscriptions for these topics with its neighbors, unless a subscription already exists. This is shown in Figure 6.
When an application publishes information, the receiving broker forwards it (possibly through one or more other brokers) to any applications that have valid subscriptions for it, including applications registered at other brokers supporting this stream (for global publications). This is shown in Figure 7.
When a broker sends any publish or subscribe message to another broker, it sets its own user ID in the message, and uses its own authority to put the message. This means that the broker must have the authority to put messages onto other brokers' queues (unless the channel is set up to put incoming messages with the message channel agent's authority). This also means that all authorization checks are performed at the publisher's or subscriber's local broker.
For more information about brokers, see Managing the broker.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
amqnar1012 |