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
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.
The text was updated successfully, but these errors were encountered:
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 aCommand
, but should be able to handleCommands
received from clients and then route eachCommandResponse
to the appropriate client.The text was updated successfully, but these errors were encountered: