FluxFlow.Components.Http
7.0.0-rc.1
dotnet add package FluxFlow.Components.Http --version 7.0.0-rc.1
NuGet\Install-Package FluxFlow.Components.Http -Version 7.0.0-rc.1
<PackageReference Include="FluxFlow.Components.Http" Version="7.0.0-rc.1" />
<PackageVersion Include="FluxFlow.Components.Http" Version="7.0.0-rc.1" />
<PackageReference Include="FluxFlow.Components.Http" />
paket add FluxFlow.Components.Http --version 7.0.0-rc.1
#r "nuget: FluxFlow.Components.Http, 7.0.0-rc.1"
#:package FluxFlow.Components.Http@7.0.0-rc.1
#addin nuget:?package=FluxFlow.Components.Http&version=7.0.0-rc.1&prerelease
#tool nuget:?package=FluxFlow.Components.Http&version=7.0.0-rc.1&prerelease
FluxFlow.Components.Http
Standalone workflow-value HTTP client node. It depends on Nodes, not Composition or Engine.
HttpClientNode physically accepts and emits FlowMessage<FlowValue>. It owns
materialization from the public workflow shape to its private HttpClientRequest
and serializes HttpResponseResult back to FlowValue. Requests contain method,
URL, headers, optional exact FlowContent body, and optional timeout. Responses
preserve status, headers, exact bounded body, content metadata, truncation state,
and status classification.
await using var node = new HttpClientNode(httpClient);
var results = new BufferBlock<FlowMessage<FlowValue>>();
node.Output.LinkTo(results);
await node.Input.SendAsync(FlowMessage.Create<FlowValue>(FlowValue.From(new
{
method = "POST",
url = "v1/items",
body = new { orderId = 42 }
})));
var response = await results.ReceiveAsync();
if (!response.IsError)
Console.WriteLine(response.Value.ToJsonElement().GetProperty("statusCode"));
Invalid requests, timeout, network/send/read failure, and configured non-success
handling become FlowError on Output. There is no separate failure result or
Errors port. Non-success responses remain normal HttpResponseResult values by
default; TreatNonSuccessStatusAsError changes that policy.
The host supplies and owns HttpClient, including base address, pooling,
authentication, TLS, redirects, proxy, retry, and endpoint policy. The node
never disposes it. Response decoding is explicit downstream; the HTTP node
preserves bytes and declared content metadata.
Composition
Install FluxFlow.Components.Http.Composition for optional FluxFlow.Composition factories and Designer metadata. This runtime package remains free of Composition, Designer, and Engine dependencies.
| 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
- FluxFlow.Nodes (>= 5.0.0-rc.1)
-
net8.0
- FluxFlow.Nodes (>= 5.0.0-rc.1)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on FluxFlow.Components.Http:
| Package | Downloads |
|---|---|
|
FluxFlow.Components.Http.AspNetCore
ASP.NET Core HTTP trigger adapter for FluxFlow: maps an endpoint's HttpContext onto the request/reply bridge so an inbound request flows into a graph and the correlated response is written back. The only FluxFlow package that references ASP.NET Core. |
|
|
FluxFlow.Components.Http.Composition
Canonical HTTP FlowContent/result registration and Designer metadata over host-owned keyed HttpClient resources. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 7.0.0-rc.1 | 101 | 9/5/2026 |
| 6.0.0 | 264 | 8/3/2026 |
| 3.0.2 | 155 | 7/3/2026 |
| 3.0.1 | 219 | 7/2/2026 |
| 3.0.0 | 162 | 6/19/2026 |
| 2.0.0 | 148 | 6/18/2026 |
| 1.2.1 | 132 | 6/15/2026 |
| 1.2.0 | 430 | 6/12/2026 |
| 1.1.0 | 130 | 6/5/2026 |
| 1.0.0 | 127 | 6/4/2026 |
| 0.2.0-alpha.1 | 262 | 6/2/2026 |
| 0.1.1-alpha.1 | 103 | 6/2/2026 |
| 0.1.0-alpha.1 | 111 | 6/1/2026 |
Breaking dependency upgrade: rebuilt for the canonical runtime and event contracts. Adopt the coordinated package set and recompile consumers; no legacy compatibility transport is provided.