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

TCP bus does not properly route messages from single server to multiple clients #109

Open
joshkempner opened this issue May 10, 2022 · 1 comment
Assignees
Labels

Comments

@joshkempner
Copy link
Contributor

The server-side implementation of the TCP message bus broadcasts all outgoing messages to all clients, instead of routing them to the appropriate client.

With Events it's tough to know where a given message should be routed unless it has a non-empty causation ID that can be matched up with the message ID of a received message.

With Commands, it's quite a bit more straightforward. Servers should never initiate the sending of a Command, but should be able to handle Commands received from clients and then route each CommandResponse to the appropriate client.

@joshkempner joshkempner self-assigned this May 10, 2022
@joshkempner joshkempner mentioned this issue May 10, 2022
@joshkempner
Copy link
Contributor Author

#110 Resolves this for Commands and their CommandResponses. Routing of Events that are published server-side still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant