Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Routing by Channel #98

Open
Lazzaretti opened this issue Jan 6, 2021 · 0 comments
Open

Routing by Channel #98

Lazzaretti opened this issue Jan 6, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@Lazzaretti
Copy link
Member

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.

@Lazzaretti Lazzaretti added the enhancement New feature or request label Jan 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant