ioxide.httpclient
0.2.5
See the version list below for details.
dotnet add package ioxide.httpclient --version 0.2.5
NuGet\Install-Package ioxide.httpclient -Version 0.2.5
<PackageReference Include="ioxide.httpclient" Version="0.2.5" />
<PackageVersion Include="ioxide.httpclient" Version="0.2.5" />
<PackageReference Include="ioxide.httpclient" />
paket add ioxide.httpclient --version 0.2.5
#r "nuget: ioxide.httpclient, 0.2.5"
#:package ioxide.httpclient@0.2.5
#addin nuget:?package=ioxide.httpclient&version=0.2.5
#tool nuget:?package=ioxide.httpclient&version=0.2.5
A shared-nothing io_uring runtime for .NET.
One ring per reactor thread - run one per core. Each reactor owns its ring, its SO_REUSEPORT listener, its connections and its clients outright: nothing is shared, so nothing is locked. HTTP, Postgres, Redis and file I/O all submit on the owning ring and resume inline on the same thread. No thread pool on the hot path. No native dependencies - raw syscalls, nothing else.
Linux 6.1+ · .NET 10 · status
0.1.1- experimental
Documentation - architecture, guides, the full picture
First-class async/await
Shared-nothing runtimes usually ask you to give up the platform's async model. ioxide keeps it:
handlers are ordinary async Task code, and await works everywhere.
- Ring completions resume their continuations inline on the reactor thread - an awaited recv, query or file read picks up exactly where it left off, with no thread pool hop.
- A per-reactor
SynchronizationContextcatches everything that would otherwise escape: timers,HttpClient,Task.Runresults - their continuations post back to the owning reactor. - Ring operations await through reusable, allocation-free awaitables.
You always wake up on your reactor. That is what makes shared-nothing practical in .NET: connection, pool and handler state stays single-threaded without a lock in sight.
Packages
| Package | What it does |
|---|---|
ioxide |
The runtime: reactors, TCP/UDP transports, connections, the ring-native client seam. |
ioxide.pg |
Postgres driver. A pool per reactor; connect, query and stream rows on the owning ring. |
ioxide.redis |
Redis client. RESP2, pipelining, pub/sub - pooled per reactor. |
ioxide.file |
Static assets. Immutable snapshots, baked responses, positional ring reads. |
ioxide.tls |
TLS. OpenSSL handshake over the ring, then kTLS - handlers keep writing plaintext. |
ioxide.Kestrel |
ASP.NET Core transport: UseIoxide() and Kestrel runs one ring per core. |
Scope
ioxide hands you raw bytes and stays out of HTTP. Request parsing and response bytes are your
code; the runtime owns the ring, the connections and the clients. When you want a framework
on top, ioxide.Kestrel plugs the same engine under ASP.NET Core.
| 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. net11.0 is compatible. |
-
net10.0
- ioxide (>= 0.2.5)
- ioxide.http11 (>= 0.2.5)
- ioxide.nghttp2 (>= 0.2.5)
- ioxide.nghttp3 (>= 0.2.5)
- ioxide.ngtcp2 (>= 0.2.5)
-
net11.0
- ioxide (>= 0.2.5)
- ioxide.http11 (>= 0.2.5)
- ioxide.nghttp2 (>= 0.2.5)
- ioxide.nghttp3 (>= 0.2.5)
- ioxide.ngtcp2 (>= 0.2.5)
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.4.177 | 0 | 8/10/2026 |
| 0.4.176 | 0 | 8/10/2026 |
| 0.4.169 | 33 | 8/9/2026 |
| 0.4.168 | 35 | 8/9/2026 |
| 0.4.167 | 36 | 8/9/2026 |
| 0.4.165 | 41 | 8/9/2026 |
| 0.4.163 | 48 | 8/8/2026 |
| 0.4.162 | 33 | 8/8/2026 |
| 0.4.161 | 43 | 8/8/2026 |
| 0.4.156 | 41 | 8/8/2026 |
| 0.4.153 | 39 | 8/7/2026 |
| 0.4.152 | 41 | 8/7/2026 |
| 0.3.149 | 53 | 8/7/2026 |
| 0.3.145 | 56 | 8/5/2026 |
| 0.3.100 | 40 | 8/5/2026 |
| 0.2.6 | 47 | 8/4/2026 |
| 0.2.5 | 44 | 8/4/2026 |