Building a resumable upload server with SwiftNIO

At a glance

Project structure

Source bundle/
├── Dependencies/
│   └── swift-http-types/
│       └── Sources/
│           ├── HTTPTypesNIOHTTP2/
│           │   ├── HTTP2ToHTTPCodec.swift
│           │   └── HTTP2HeadersStateMachine.swift
│           ├── HTTPTypes/
│           │   ├── HTTPField.swift
│           │   ├── HTTPFields.swift
│           │   ├── HTTPRequest.swift
│           │   └── HTTPResponse.swift
│           └── HTTPTypesNIOHTTP1/
│               ├── HTTP1ToHTTPCodec.swift
│               └── HTTPToHTTP1Codec.swift
└── Sources/
    └── NIOResumableUpload/
        ├── HTTPResumableUploadHandler.swift
        ├── HTTPResumableUploadProtocol.swift
        ├── HTTPResumableUpload.swift
        └── HTTPResumableUploadChannel.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 0 project/configuration file(s) and 42 source declaration(s).

Overall architecture

flowchart LR
    N1["BaseClientCodec"]
    N2["HTTPResumableUploadHandler"]
    N3["FoundationNetworking APIs"]
    N1 --> N2
    N2 --> N3

Reference code

Dependencies/swift-http-types/Sources/HTTPTypesNIOHTTP2/HTTP2ToHTTPCodec.swift:29 — architecture anchor

private struct BaseClientCodec {
    private var headerStateMachine: HTTP2HeadersStateMachine = HTTP2HeadersStateMachine(mode: .client)
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Foundation.

Ownership and state

classDiagram
    HTTPField o-- Name : name
    HTTPField o-- Self : rawValue
    HTTPField o-- DynamicTableIndexingStrategy : indexingStrategy
    _Storage *-- Array : fields

Ownership evidence

Dependencies/swift-http-types/Sources/HTTPTypes/HTTPField.swift:45 — stored dependency or nearest verified ownership anchor

public struct HTTPField: Sendable, Hashable {
    // ...
        self.name = name
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

Dependencies/swift-http-types/Sources/HTTPTypes/HTTPField.swift:25 — representative execution boundary

public struct HTTPField: Sendable, Hashable {
    // ...
        case automatic
    // ...
}

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

Sources/NIOResumableUpload/HTTPResumableUploadHandler.swift:13 — representative type boundary

public final class HTTPResumableUploadHandler: ChannelDuplexHandler {
    public typealias InboundIn = HTTPTypeServerRequestPart
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

Dependencies/swift-http-types/Sources/HTTPTypes/HTTPField.swift:44 — representative boundary

    public init(name: Name, value: some StringProtocol) {
        self.name = name
        self.rawValue = Self.legalizeValue(ISOLatin1String(value))
    }

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: Handler: HTTPResumableUploadHandler; Recorder: InboundRecorder.
• Protocols: no local protocol declaration in the scanned source.
• Methods: processInboundData, processOutboundData, channelRead, write, handlerAdded, channelActive, channelInactive, channelReadComplete.
• Files: Sources/NIOResumableUpload/HTTPResumableUploadHandler.swift, Sources/NIOResumableUpload/HTTPResumableUploadProtocol.swift, Dependencies/swift-http-types/Sources/HTTPTypes/HTTPField.swift, Dependencies/swift-http-types/Sources/HTTPTypes/HTTPFields.swift, Dependencies/swift-http-types/Sources/HTTPTypes/HTTPRequest.swift, Dependencies/swift-http-types/Sources/HTTPTypes/HTTPResponse.swift.

Architecture takeaways

• BaseClientCodec is the main source-visible entry or composition anchor for this sample.
• Framework work reaches HTTPTypes, NIOCore, HTTPTypesNIO, FoundationNetworking through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation