Name: Alamofire
Owner: DuckDuckGo
Description: Elegant HTTP Networking in Swift
Forked from: Alamofire/Alamofire
Created: 2018-02-08 17:48:42.0
Updated: 2018-02-08 17:48:45.0
Pushed: 2018-02-08 12:42:11.0
Size: 5119
Language: Swift
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Alamofire is an HTTP networking library written in Swift.
In order to keep Alamofire focused specifically on core networking implementations, additional component libraries have been created by the Alamofire Software Foundation to bring additional functionality to the Alamofire ecosystem.
UIImage and UIImageView extensions, custom image filters, an auto-purging in-memory cache and a priority-based image downloading system.URLSession instances not managed by Alamofire.CocoaPods is a dependency manager for Cocoa projects. You can install it with the following command:
m install cocoapods
CocoaPods 1.1+ is required to build Alamofire 4.0+.
To integrate Alamofire into your Xcode project using CocoaPods, specify it in your Podfile:
ce 'https://github.com/CocoaPods/Specs.git'
form :ios, '10.0'
frameworks!
et '<Your Target Name>' do
pod 'Alamofire', '~> 4.5'
Then, run the following command:
d install
Carthage is a decentralized dependency manager that builds your dependencies and provides you with binary frameworks.
You can install Carthage with Homebrew using the following command:
ew update
ew install carthage
To integrate Alamofire into your Xcode project using Carthage, specify it in your Cartfile:
ub "Alamofire/Alamofire" ~> 4.5
Run carthage update to build the framework and drag the built Alamofire.framework into your Xcode project.
The Swift Package Manager is a tool for automating the distribution of Swift code and is integrated into the swift compiler. It is in early development, but Alamofire does support its use on supported platforms.
Once you have your Swift package set up, adding Alamofire as a dependency is as easy as adding it to the dependencies value of your Package.swift.
ndencies: [
.Package(url: "https://github.com/Alamofire/Alamofire.git", majorVersion: 4)
ndencies: [
.package(url: "https://github.com/Alamofire/Alamofire.git", from: "4.0.0")
If you prefer not to use any of the aforementioned dependency managers, you can integrate Alamofire into your project manually.
Open up Terminal, cd into your top-level project directory, and run the following command “if” your project is not initialized as a git repository:
t init
Add Alamofire as a git submodule by running the following command:
t submodule add https://github.com/Alamofire/Alamofire.git
Open the new Alamofire folder, and drag the Alamofire.xcodeproj into the Project Navigator of your application's Xcode project.
It should appear nested underneath your application's blue project icon. Whether it is above or below all the other Xcode groups does not matter.
Select the Alamofire.xcodeproj in the Project Navigator and verify the deployment target matches that of your application target.
Next, select your application project in the Project Navigator (blue project icon) to navigate to the target configuration window and select the application target under the “Targets” heading in the sidebar.
In the tab bar at the top of that window, open the “General” panel.
Click on the + button under the “Embedded Binaries” section.
You will see two different Alamofire.xcodeproj folders each with two different versions of the Alamofire.framework nested inside a Products folder.
It does not matter which
Productsfolder you choose from, but it does matter whether you choose the top or bottomAlamofire.framework.
Select the top Alamofire.framework for iOS and the bottom one for OS X.
You can verify which one you selected by inspecting the build log for your project. The build target for
Alamofirewill be listed as eitherAlamofire iOS,Alamofire macOS,Alamofire tvOSorAlamofire watchOS.
And that's it!
The
Alamofire.frameworkis automagically added as a target dependency, linked framework and embedded framework in a copy files build phase which is all you need to build on the simulator and a device.
The following radars have some effect on the current implementation of Alamofire.
rdar://21349340 - Compiler throwing warning due to toll-free bridging issue in test caserdar://26870455 - Background URL Session Configurations do not work in the simulatorrdar://26849668 - Some URLProtocol APIs do not properly handle URLRequestrdar://36082113 - URLSessionTaskMetrics failing to link on watchOS 3.0+The following radars have been resolved over time after being filed against the Alamofire project.
rdar://26761490 - Swift string interpolation causing memory leak with common usage (Resolved on 9/1/17 in Xcode 9 beta 6).Alamofire is named after the Alamo Fire flower, a hybrid variant of the Bluebonnet, the official state flower of Texas.
Simple, static data such as paths, parameters and common headers belong in the Router. Dynamic data such as an Authorization header whose value can changed based on an authentication system belongs in a RequestAdapter.
The reason the dynamic data MUST be placed into the RequestAdapter is to support retry operations. When a Request is retried, the original request is not rebuilt meaning the Router will not be called again. The RequestAdapter is called again allowing the dynamic data to be updated on the original request before retrying the Request.
Alamofire is owned and maintained by the Alamofire Software Foundation. You can follow them on Twitter at @AlamofireSF for project updates and releases.
If you believe you have identified a security vulnerability with Alamofire, you should report it as soon as possible via email to security@alamofire.org. Please do not post it to a public issue tracker.
The ASF is looking to raise money to officially register as a federal non-profit organization. Registering will allow us members to gain some legal protections and also allow us to put donations to use, tax free. Donating to the ASF will enable us to:
The community adoption of the ASF libraries has been amazing. We are greatly humbled by your enthusiasm around the projects, and want to continue to do everything we can to move the needle forward. With your continued support, the ASF will be able to improve its reach and also provide better legal safety for the core members. If you use any of our libraries for work, see if your employers would be interested in donating. Our initial goal is to raise $1000 to get all our legal ducks in a row and kickstart this campaign. Any amount you can donate today to help us reach our goal would be greatly appreciated.
Alamofire is released under the MIT license. See LICENSE for details.