-
Notifications
You must be signed in to change notification settings - Fork 59
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
Support for sending commands from message handlers #11
Comments
I added a small extension Usage is like so:
awaiting ctx.LocalSaga will pause the command processing until the saga function is complete. |
Which operates a NSB saga to perform commands in order
Working on the feature - syntax is going to be
Under the covers we'll be running a normal NSB saga which will keep track of the commands already sent and accepted. If any command is rejected the abort commands will be run in order and the originating message will be sent to the error queue |
In NSB 6 I can't use request / response in message handlers - see Particular/NServiceBus.Callbacks#42
The "correct" way to do this from what I'm told is to setup a saga which can collect replies from normal Sends and handle timeouts / retries and such in itself.
It sounds good - and sounds like something we can include in the library so users won't have to deal with that logic themselves
The text was updated successfully, but these errors were encountered: