Alamofire VS Socket.IO

Alamofire is a swift http request lib. By default, we need use completion handler to handle response. Today we are going to find out how to use it with async and await.

Alamofire - Elegant HTTP networking

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

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] )

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

Based on Swift and constantly updated, it’s probably the most used library on iOS. Don’t worry, this is the best and only library you can use for HTTP requests. You can find more info on Alamofire here.

Socket.IO - Socket.IO client written on Swift. Language: Swift.

I am running socket.io on an Apache server through Python Flask. We're integrating it into an iOS app (using the Socket.IO-Client-Swift library) and we're having a weird issue.

Yeah, I am using https://github.com/socketio/socket.io-client-swift with my Xcode project, and server in nodejs.