WalFlow.Signals.AspNetCore
0.1.0-alpha.alpha.20260708090623
dotnet add package WalFlow.Signals.AspNetCore --version 0.1.0-alpha.alpha.20260708090623
NuGet\Install-Package WalFlow.Signals.AspNetCore -Version 0.1.0-alpha.alpha.20260708090623
<PackageReference Include="WalFlow.Signals.AspNetCore" Version="0.1.0-alpha.alpha.20260708090623" />
<PackageVersion Include="WalFlow.Signals.AspNetCore" Version="0.1.0-alpha.alpha.20260708090623" />
<PackageReference Include="WalFlow.Signals.AspNetCore" />
paket add WalFlow.Signals.AspNetCore --version 0.1.0-alpha.alpha.20260708090623
#r "nuget: WalFlow.Signals.AspNetCore, 0.1.0-alpha.alpha.20260708090623"
#:package WalFlow.Signals.AspNetCore@0.1.0-alpha.alpha.20260708090623
#addin nuget:?package=WalFlow.Signals.AspNetCore&version=0.1.0-alpha.alpha.20260708090623&prerelease
#tool nuget:?package=WalFlow.Signals.AspNetCore&version=0.1.0-alpha.alpha.20260708090623&prerelease
WalFlow.Signals.AspNetCore
ASP.NET Core HTTP incremental snapshot signaling channel plugin for WalFlow.
Adds SignalChannel.AspNetHttp support using an in-process queue populated by an HTTP endpoint.
Install
dotnet add package WalFlow.Signals.AspNetCore
Configuration
services.AddWalFlowAspNetSignalChannel(options =>
{
options.QueueName = "default";
});
AspNetSignalChannelOptions:
| Property | Type | Default | Description |
|---|---|---|---|
QueueName |
string |
"default" |
Logical queue name used by endpoint + polling channel |
Usage
Service registration:
services.AddWalFlowAspNetSignalChannel(options =>
{
options.QueueName = "default";
});
services.AddAuthorization(options =>
{
options.AddPolicy("walflow-signals", policy => policy.RequireAuthenticatedUser());
});
services.Configure<CdcProcessorOptions>(opt =>
{
opt.Signaling.EnabledChannels = [SignalChannel.Source, SignalChannel.AspNetHttp];
});
Endpoint mapping:
app.MapWalFlowSignalEndpoint(
pattern: "/walflow/signals",
options: new WalFlowSignalEndpointOptions
{
QueueName = "default",
AuthorizationPolicy = "walflow-signals"
});
For local-only scenarios, anonymous access must be explicit:
app.MapWalFlowSignalEndpoint(
pattern: "/walflow/signals",
options: new WalFlowSignalEndpointOptions
{
QueueName = "default",
AllowAnonymous = true
});
HTTP Payload Format
POST /walflow/signals accepts either:
- one JSON signal object
- array of signal objects
Signal object format:
{
"id": "sig-1",
"type": "execute-snapshot",
"data": { "data-collections": ["public.orders"], "type": "incremental" }
}
Notes
QueueNamein plugin options should match endpointQueueName.- Endpoint mapping requires either
AuthorizationPolicyor explicitAllowAnonymous = true. - Validation fails startup if
SignalChannel.AspNetHttpis enabled with empty queue name.
| 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
- Npgsql (>= 10.0.3)
- WalFlow.Abstractions (>= 0.1.0-alpha.alpha.20260708090623)
- WalFlow.Sources.Postgres (>= 0.1.0-alpha.alpha.20260708090623)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on WalFlow.Signals.AspNetCore:
| Package | Downloads |
|---|---|
|
WalFlow
Meta-package that pulls in the full WalFlow CDC stack for consumers who want the default everything-included setup. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.1.0-alpha.alpha... | 83 | 7/8/2026 |
| 0.1.0-alpha.alpha... | 88 | 3/30/2026 |