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
One weakness in how the MessageSequence extension is working is that it listens to messages with the same routing key as any other subscriber for that message. This means that if the message it is listening for is published a lot, it will receive it multiple times while still only being interested in a couple of those. When #73 is done, we should make sure that the extension binds for a specific message id ([routingkey].[globalmessageid). This way, only messages for the specific message sequence is routed to the queue. Once a message sequence is finished, it should remove the bindings for that sequence. As a consequence, to this we will have a slight performance hit in creating a sequence as it will have to make more roundtrips to the broker
The text was updated successfully, but these errors were encountered:
This is because when a message sequence is completed, we want to get the config
for a message type and we only have the type. Instead of constructing a generic
argument, I find it cleaner to add methods that takes a Type argument, too.
One weakness in how the
MessageSequence
extension is working is that it listens to messages with the same routing key as any other subscriber for that message. This means that if the message it is listening for is published a lot, it will receive it multiple times while still only being interested in a couple of those. When #73 is done, we should make sure that the extension binds for a specific message id ([routingkey].[globalmessageid
). This way, only messages for the specific message sequence is routed to the queue. Once a message sequence is finished, it should remove the bindings for that sequence. As a consequence, to this we will have a slight performance hit in creating a sequence as it will have to make more roundtrips to the brokerThe text was updated successfully, but these errors were encountered: