Skip to content

helje5/NWHTTPProtocol

develop
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 
 
 

NWHTTPProtocol

Swift5 macOS iOS

An HTTP protocol parser (aka NWProtocolFramer) for the Apple Network.framework.

How it works is described in my blog entry: Intro to Network.framework Servers.

Network.framework requires iOS 13+ / macOS 10.15+.

This is intentionally kept very simple and basic. E.g. it does not define Swift types for HTTP requests and the like, but puts the status/request/URI in plain Message metadata fields.

The protocol is just wrapping the (embedded) http_parser.c/h developed as part of the Node.js project.

NWHTTPServer

It also includes NWHTTPServer, a very simple HTTP server based on the NWHTTPProtocol.

Example:

let server = HTTPServer { request, response in
    print("Received:", request)
    try response.send("Hello!\n")
}
server.run()

Production

Note that for production use I'd suggest to not use a protocol framer for HTTP. Instead hookup http_parser.c to plain Network.framework (as shown for echo in the blog article). At least that's what I do in production apps. NW protocol framing isn't really required for http_parser.c, because that already does all the framing necessary and can be fed asynchronously).

Who

NWHTTPProtocol is brought to you by ZeeZide. We like feedback, GitHub stars, cool contract work, presumably any form of praise you can think of.

About

An HTTP protocol implementation (an `NWProtocolFramer`) and a tiny HTTP server for Network.framework

Resources

License

Stars

Watchers

Forks

Packages

No packages published