Http Client

Table of Contents

• Dependencies
• Features
• Status
• Description
• Details
  • HttpClient
  • HttpClientRequest
  • HttpClientResponse
  • HttpClientRequestBodyProvider
  • HttpClientOperationListener
  • HttpClientOperationNotifier
  • HttpClientResponseBuffer
  • HttpClientOperationEvent
  • HttpClientOperationMemory
  • HttpClientOperation
  • Async Adapter
• Examples
• Roadmap
• Statistics

🟥 Streaming-first HTTP client with native OS backends

SC::HttpClient is a streaming-first HTTP client built on native OS backends.

Dependencies

• Dependencies: Foundation
• All dependencies: Foundation

Features

• Native OS backends (NSURLSession on Apple, WinHTTP on Windows, libcurl on Linux)
• Poll-driven core API with an optional HttpClientAsyncT adapter for AsyncStreams
• Inline or streamed request bodies with explicit size
• Async streaming integration available through SC::HttpClientAsyncT
• Blocking helper for simple synchronous workflows

Status

🟥 Draft
The API is stabilizing and the streaming core is in place, but consider everything HIGHLY experimental.

Description

HttpClient is designed to stay allocation-free by relying on caller-provided buffers and queues. The core library is poll-driven and independent from Async, AsyncStreams, Threading, and Time. Response headers are written into a user-provided buffer, while response body chunks are delivered during poll() through a small listener interface.

Request bodies can be passed as a fixed span or streamed by implementing a pull-based provider with an explicit Content-Length. For stream-first integration there is a separate SC::HttpClientAsyncT<T_AsyncEventLoop, T_AsyncStreams> adapter that translates the same core operation into AsyncReadableStream and AsyncWritableStream.

Current limitations:

• One in-flight request per SC::HttpClient
• Chunked request bodies are not fully supported on all backends
• Redirects disabled by default
• HTTP/2 only when provided by the OS backend

Details

HttpClient

Reusable HTTP backend/session owner.

HttpClientRequest

Configuration for an outgoing HTTP request.

HttpClientResponse

Parsed response metadata filled when headers arrive.

HttpClientRequestBodyProvider

Pull-based provider for streamed request bodies.

HttpClientOperationListener

Listener receiving response notifications during HttpClientOperation::poll.

HttpClientOperationNotifier

Optional notifier used by external adapters to wake up their own event loop.

HttpClientResponseBuffer

Caller-owned response buffer descriptor for one HttpClientOperation.

HttpClientOperationEvent

Event slot storage used by HttpClientOperation to hand off backend notifications.

HttpClientOperationMemory

Caller-owned memory for one HttpClientOperation.

HttpClientOperation

One in-flight HTTP request/response operation.

Async Adapter

SC::HttpClientAsyncT and SC::HttpClientAsyncOperationMemoryT are declared in Libraries/HttpClient/HttpClientAsync.h.

They provide the optional Async / AsyncStreams integration layer on top of the poll-driven HttpClientOperation core, reusing the same request, response, and caller-owned operation memory model.

With the standard Async Streams library, instantiate the adapter as SC::HttpClientAsyncT<SC::AsyncEventLoop, SC::AsyncStreams> and the adapter memory as SC::HttpClientAsyncOperationMemoryT<SC::AsyncStreams>.

Examples

• Unit tests in Tests/Libraries/HttpClient show blocking and async usage patterns
• AsyncStreams examples show how to integrate streaming pipelines with AsyncReadableStream

Roadmap

🟨 MVP

• Chunked transfer encoding for request bodies
• Multi-inflight support (one client managing multiple concurrent requests)

🟩 Usable Features:

• Expanded redirect policy controls
• Optional TLS configuration hooks

🟦 Complete Features:

• Pluggable backend selection

💡 Unplanned Features:

• HTTP/3

Statistics

Type	Lines Of Code	Comments	Sum
Headers	200	85	285
Sources	1950	318	2268
Sum	2150	403	2553