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
Currently, the router routes messages to ports.
However, most messaging protocols know the concept of channels.
It would be nice if the routing does not only allow a port destination but also a port+channel destination.
Example:
We have an AMQP Port that is connected to a RabbitMQ Service called port A.
Port A has a configuration of two exchanges: Exchange 1 and exchange 2.
Messages can be routed to port A.
Port A currently forwards the messages to all configured exchanges (1&2) on RabbitMQ.
It would be nice to be able to select the destination port AND channel, e.g., port A & exchange 1.
Workaround:
One port per channel group that should be addressable has to be configured.
This means that there is an overhead of multiple TCP connections to the same service.
For the example this means: Port A with exchange 1 and port B with exchange 2 have to be configured.
The text was updated successfully, but these errors were encountered:
Currently, the router routes messages to ports.
However, most messaging protocols know the concept of channels.
It would be nice if the routing does not only allow a port destination but also a port+channel destination.
Example:
We have an AMQP Port that is connected to a RabbitMQ Service called port A.
Port A has a configuration of two exchanges: Exchange 1 and exchange 2.
Messages can be routed to port A.
Port A currently forwards the messages to all configured exchanges (1&2) on RabbitMQ.
It would be nice to be able to select the destination port AND channel, e.g., port A & exchange 1.
Workaround:
One port per channel group that should be addressable has to be configured.
This means that there is an overhead of multiple TCP connections to the same service.
For the example this means: Port A with exchange 1 and port B with exchange 2 have to be configured.
The text was updated successfully, but these errors were encountered: