Perfect VS Alamofire

There are some interesting http frameworks (think Express.js, Fastify, etc.) to simplify working with SwiftNIO such as Vapor, Hummingbird and Perfect. There's even a full CMS (Feather).

Alamofire - Alamofire is an HTTP networking library written in Swift. (de facto standard library for network) Language: Swift.

You can find an example using Alamofire, the most commonly used network framework, here.

https://github.com/Alamofire/Alamofire/blob/master/Documenta...

To add Alamofire, we'll be using Swift Package Manager. Xcode comes with built-in support for it and we'll not have to use external package managers like Cocoapods or Carthage. Click on File → Add Packages...

import ProjectDescription let dependencies = Dependencies( carthage: [ .github(path: "Alamofire/Alamofire", requirement: .exact("5.0.4")), ], swiftPackageManager: [ .remote(url: "https://github.com/Alamofire/Alamofire", requirement: .upToNextMajor(from: "5.0.0")), ], platforms: [.iOS] )

I have a prototype on a branch. Right now it's just continuations that wrap the completion handler API and may change significantly over time. The other APIs won't really change until we can rewrite major portions to the new async features.

https://github.com/Alamofire/Alamofire/blob/master/Documentation/Usage.md#get-request-with-url-encoded-parameters

You can checkout Request Parameters and Parameter Encoders for more details

AlamoFire doesn’t support background configurations. Makes it impossible for my company to use AlamoFire for the one part of the app where it’d be useful as we support uploading/downloading unlimited numbers of files at a time (data driven app with offline support). If you’re downloading/uploading 10GB of data, you don’t want to be stuck sitting in an app waiting for it to finish... I’d be shocked if it’s an industry standard with such an important core feature missing.