Introduction to AsyncHTTPClient
summary
A cross‑platform HTTP client built on SwiftNIO that targets server workloads and uses event loop sharing to avoid thread explosion. It delivers both fully buffered requests/responses and a streaming API with delegate callbacks, implements backpressure via futures to stop reading until handlers complete, supports TLS, redirects, timeouts and proxies, and is shipping enough to use today while planning connection pooling and HTTP/2 for the 1.0 release.
AI-written summary · about
chapters (28)
- 0:00Intro
- 1:22Welcome
- 1:44Authors
- 2:33Community
- 3:09Why AsyncHTTPClient
- 3:27What about URLSession
- 4:58Synchronous Decoupling
- 5:47Problems with Microservices
- 9:29Layering
- 10:07Pipeline
- 10:46HTTP Pipeline
- 11:28Features
- 11:44Event Loop
- 12:06Thread Pool
- 13:12Event Loop Group
- 13:29HTTP Client
- 13:48HTTP Response
- 14:27Streaming API
- 16:14HTTP Delegate
- 18:00Backpressure
- 18:31Streaming
- 19:14Future
- 20:01TLS
- 20:41Redirects
- 21:01Timeouts
- 21:23Proxy
- 21:36Next steps
- 22:55How to get involved
related talks
22mEvent driven networking for Swift
21mSwift NIO, Vapor, and Server Concurrency
05mSwift Superpowers #2
18mImplementing JSON-RPC with SwiftNIO
09mIntroduction to Hummingbird 2
39mWe need to talk about Websockets
35mThe Multi-Threaded Asynchronous Parallel World of Swift
40mThe Knights Who Say NIO: SwiftNIO in Depth