Scry.Server.Wolverine
0.1.0-beta.13
dotnet add package Scry.Server.Wolverine --version 0.1.0-beta.13
NuGet\Install-Package Scry.Server.Wolverine -Version 0.1.0-beta.13
<PackageReference Include="Scry.Server.Wolverine" Version="0.1.0-beta.13" />
<PackageVersion Include="Scry.Server.Wolverine" Version="0.1.0-beta.13" />
<PackageReference Include="Scry.Server.Wolverine" />
paket add Scry.Server.Wolverine --version 0.1.0-beta.13
#r "nuget: Scry.Server.Wolverine, 0.1.0-beta.13"
#:package Scry.Server.Wolverine@0.1.0-beta.13
#addin nuget:?package=Scry.Server.Wolverine&version=0.1.0-beta.13&prerelease
#tool nuget:?package=Scry.Server.Wolverine&version=0.1.0-beta.13&prerelease
Scry.Server.Wolverine
Carries Scry commands over Wolverine: a command a client sends is sent to the handler that handles it, and its outcome comes back to the client when the handler is done.
On the Scry server:
builder.Services.AddScry<SampleContext>(
_ =>
{
_.MaxPendingCommands = 100;
_.UseWolverineCommands(_ => _.For<RepriceOrder>());
});
builder.Host.UseWolverine(
_ =>
{
_.AddScryCommandCompletions();
_.PublishMessage<RepriceOrder>().ToRabbitQueue("worker");
});
On the worker:
builder.Host.UseWolverine(
_ =>
{
_.UseScryCommands();
_.Policies.OnAnyException()
.RetryTimes(3)
.Then.MoveToErrorQueue()
.AndScryFailure();
});
The server validates, authorizes and binds the command as it would for an in-process handler, then sends it with the command's id and caller as headers, routed by the application's own routing. The handler is an ordinary Wolverine handler. Once it has returned, middleware responds to the node that sent the command. A message that ends in the error queue is answered as failed by AndScryFailure, added to the error policy that sends it there. A handler of a command with a result answers with context.SetScryResult(result): its return value cascades as messages, so the result travels apart from it.
It claims nothing until told: a Wolverine message is any class. Everything it does not claim stays with its in-process handler.
This package carries no change backplane. A handler's writes reach live queries through the notification the server raises on completion for a targeted command, a change probe, or the poll.
Docs: Commands
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | 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
- Microsoft.EntityFrameworkCore (>= 10.0.12)
- Scry.Server (>= 0.1.0-beta.13)
- WolverineFx (>= 6.46.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.1.0-beta.13 | 0 | 10/7/2026 |
| 0.1.0-beta.12 | 43 | 10/1/2026 |
| 0.1.0-beta.11 | 45 | 9/30/2026 |
| 0.1.0-beta.10 | 55 | 9/24/2026 |