You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our use-case is to federate between Rabbit and some other AMQP 1.0 compliant broker to bridge disparate systems together across enterprises. Had we had Rabbit everywhere, we would have used the protocol that works best in Rabbit, i.e. 0-9-1.
Since we must assume that the upstream is not Rabbit, you cannot assume there are exchanges, or that you can create internal queues there. Therefore, the upstream must be a queue that would need to be explicitly created on the upstream by the upstream administrator. In the end, though, just as existing federation plug-in works as a fully compliant 0-9-1 client, the new plug-in would work as a fully compliant 1.0 client.
There's enough interest in federation working with AMQP 1.0 endpoints. This issue is for gathering feedback on how exactly that should work.
Note: this probably should be a separate plugin.
The text was updated successfully, but these errors were encountered: