3 ms·
Looks like a great lib with a nice API, thx. Was there any reason why you chose callbacks over a Promise-like pattern for the async responses? Also do you kno
by mythz 12y ago
Looks like a great lib with a nice API, thx.
Was there any reason why you chose callbacks over a Promise-like pattern for the async responses?
Also do you know of any good HTTP Server libraries that will let you develop simple HTTP JSON services in Swift?
- wahnfrieden 12y agoSee Moya for a lib built on top of AlamoFire that adds reactive signals (fulfilling the promises use case): https://github.com/AshFurrow/Moya https://github.com/AshFurrow/Moya
- matttthompson 12y ago> Was there any reason why you chose callbacks over a Promise-like pattern for the async responses? Deeply-nested networking callbacks are a code smell, and I find that promises often do more harm by hiding those smells—or worse, obscuring the flow itself. In practice, Alamofire is mostly going to be single or at most nested two levels deep anyway.