FluxFlow.Components.Http.AspNetCore 1.0.0

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package FluxFlow.Components.Http.AspNetCore --version 1.0.0
                    


                    

                
NuGet\Install-Package FluxFlow.Components.Http.AspNetCore -Version 1.0.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="FluxFlow.Components.Http.AspNetCore" Version="1.0.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="FluxFlow.Components.Http.AspNetCore" Version="1.0.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="FluxFlow.Components.Http.AspNetCore" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add FluxFlow.Components.Http.AspNetCore --version 1.0.0
                    


                    

                
#r "nuget: FluxFlow.Components.Http.AspNetCore, 1.0.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package FluxFlow.Components.Http.AspNetCore@1.0.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=FluxFlow.Components.Http.AspNetCore&version=1.0.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=FluxFlow.Components.Http.AspNetCore&version=1.0.0
                    


                            Install as a Cake Tool

FluxFlow.Components.Http.AspNetCore

The ASP.NET Core HTTP trigger adapter for FluxFlow — and the only FluxFlow package that references ASP.NET Core. An HttpTriggerNode is a component: it is given its inbound request source (injected, keyed) and uses a RequestReplyCoordinator<HttpTriggerRequest, HttpTriggerReply> internally to correlate the reply back to the caller. The endpoint just feeds the keyed source.

builder.Services.AddFluxFlowHttpTrigger("greet", trigger =>
{
    // wire your graph: trigger.Output (requests) -> ... -> trigger.Responses (replies)
    var greeting = new GreetingNode();
    trigger.Output.LinkTo(greeting.Input);
    greeting.Output.LinkTo(trigger.Responses);
});

var app = builder.Build();
app.MapFluxFlowTrigger("/greet", "greet");   // endpoint feeds the keyed trigger by name

AddFluxFlowHttpTrigger registers a keyed request source + a keyed HttpTriggerNode fed from it, and a hosted service that starts the trigger with the app (which wires the graph and starts consuming) and disposes it on shutdown.

Without DI

For tests or manual composition, hold a coordinator and map it directly:

var coordinator = new RequestReplyCoordinator<HttpTriggerRequest, HttpTriggerReply>();
coordinator.Output.LinkTo(handler.Input);
handler.Output.LinkTo(coordinator.Responses);
app.MapFluxFlowTrigger("/hook", coordinator);

The endpoint

For each request it builds an HttpRequestContext from the HttpContext (method, path, query, headers, body), feeds it to the trigger, and holds the response open until the graph posts the correlated reply — which the context writes to HttpContext.Response. A timed-out request writes 504, an unexpected failure 500, a shutting-down trigger 503.

Pass correlationHeader to seed the correlation id from an inbound trace/request id; otherwise the coordinator mints one. All the correlation machinery lives in FluxFlow.Components.RequestReply; this package is just the HttpContext glue.

Product 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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
3.0.0-rc.1 65 9/5/2026
2.0.0 133 8/3/2026
1.0.5 126 7/3/2026
1.0.4 117 7/2/2026
1.0.0 125 6/19/2026

Initial ASP.NET Core HTTP trigger adapter: HttpTriggerNode is the trigger as a component (given a keyed request source, using a RequestReplyCoordinator internally). AddFluxFlowHttpTrigger(name, configure) registers it and MapFluxFlowTrigger(pattern, name) feeds it (plus a MapFluxFlowTrigger(pattern, coordinator) overload). HttpRequestContext writes the correlated response, or 504/500/503 on timeout/failure/shutdown.