-
Notifications
You must be signed in to change notification settings - Fork 647
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
Task-based notifications API #5449
Conversation
thoughts on these changes @SimonCropp @gbiellem ? |
...erviceBus.Core.Tests/ApprovalFiles/APIApprovals.ApproveNServiceBus.netframework.approved.txt
Outdated
Show resolved
Hide resolved
src/NServiceBus.Core/Recoverability/Settings/DelayedRetriesSettings.cs
Outdated
Show resolved
Hide resolved
src/NServiceBus.Core/Recoverability/Settings/ImmediateRetriesSettings.cs
Outdated
Show resolved
Hide resolved
src/NServiceBus.Core/Recoverability/Settings/ImmediateRetriesSettings.cs
Show resolved
Hide resolved
src/NServiceBus.Core/Recoverability/Settings/RetryFailedSettings.cs
Outdated
Show resolved
Hide resolved
Based on the opinions I heard from people chiming on this I decided to remove the sync overloads. While I think this causes more friction for users and therefore is a bad change, I can accept the argument that we never provided sync+async APIs in combination so far and that this is a more advanced API which might not be the right place to drive "new approaches" to this topic. |
@timbussmann re-request review when that's done? |
Fixes #5393
Provides a new notification API which is based on the internal notifications infrastructure which can support async notification subscribers.
The new APIs have been moved to the corresponding recoverability configuration settings and I've tried to give them more accurate and meaningful names.