Bsft.Messaging.Correlation
2.2.0
dotnet add package Bsft.Messaging.Correlation --version 2.2.0
NuGet\Install-Package Bsft.Messaging.Correlation -Version 2.2.0
<PackageReference Include="Bsft.Messaging.Correlation" Version="2.2.0" />
<PackageVersion Include="Bsft.Messaging.Correlation" Version="2.2.0" />
<PackageReference Include="Bsft.Messaging.Correlation" />
paket add Bsft.Messaging.Correlation --version 2.2.0
#r "nuget: Bsft.Messaging.Correlation, 2.2.0"
#:package Bsft.Messaging.Correlation@2.2.0
#addin nuget:?package=Bsft.Messaging.Correlation&version=2.2.0
#tool nuget:?package=Bsft.Messaging.Correlation&version=2.2.0
Bsft.Messaging.Correlation
The bridge between the Bsft.Correlation family and the Bsft.Messaging family: an integration event
staged while handling a request carries that request's correlation id into a delivery that may happen much
later and in another service.
Install
dotnet add package Bsft.Messaging.Correlation
Requires Bsft.Correlation and Bsft.Messaging.Abstractions, and no further Bsft packages. It bridges
the two deliberately rather than either family referencing the other: the messaging packages must not
drag the ASP.NET Core request pipeline into a background dispatcher.
Register
services.AddBsftMessagingCorrelation();
Nothing else is required, and the call has no order to observe: it registers its accessor with a plain
Add rather than TryAdd, so it replaces the ambient-only default of AddBsftMessaging whichever way
round the two are called. Both families still have to be registered themselves —
AddBsftCorrelation for the request context and AddBsftMessaging for the ambient message scope.
Configure
None. The package has no options type: what it does is decided entirely by the two families it joins.
Extend
IMessageCorrelationAccessor is the seam this package fills, and it is declared in
Bsft.Messaging.Abstractions. What this package supplies is
CorrelationContextMessageAccessor, which prefers the ambient id of a message being handled over the
scope's own: without that precedence a chain of integration events — a handler that stages the next one —
would start a fresh correlation on every hop, because the delivery runs in a new service scope whose
CorrelationContext mints a new id. Replace the accessor to take the id from somewhere else; there is no
seam of this package's own to replace.
Documentation
Topic page: docs/messaging.md. Conventions: docs/package-conventions.md.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Bsft.Correlation (>= 2.2.0)
- Bsft.Messaging.Abstractions (>= 2.2.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.12)
-
net8.0
- Bsft.Correlation (>= 2.2.0)
- Bsft.Messaging.Abstractions (>= 2.2.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 9.0.19)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.