4 ms·

A much easier way to add async HTTP and image requests would be to just use AFNetworking (https://github.com/gowalla/AFNetworking https://github.com/gowalla/AFN

• Greenisus 15y ago
  How is AFNetworking easier than ASIHTTPRequest?
  • matttthompson 15y ago
    Simple block-based API, significantly less lines of code to accomplish the same tasks, and smaller, more understandable codebase that uses Foundation classes (e.g. NSURLRequest, NSURLResponse, etc.), rather than re-inventing the wheel And though I don't have the exact numbers, AFNetworking is really fast, maybe 2-3x over ASI in average cases, from my experience and what other users report. Take a look at the examples in the README and compare that to how you'd do the same in ASI.
    • stevenp 15y ago
      This is awesome. Thanks for the tip.
    • hamedh 15y ago
      doesn't ASI also use blocks? its syntax is very similar. but i didn't know about that it's much faster than ASI, thanks for that
• stevenp 15y ago
  AFNetworking looks great, but I'm also curious as to what the advantage is over ASIHTTPRequest.
• Zev 15y ago
  I typically use PullToRefresh from https://github.com/leah/PullToRefresh https://github.com/leah/PullToRefresh instead of EGOTableViewPullRefresh. It positions itself as a superclass that handles all of the logic, rather than an external object that handles the delegate methods (as EGO does).
• lukeredpath 15y ago
  Obligatory plug for Resty: https://github.com/lukeredpath/LRResty https://github.com/lukeredpath/LRResty ;)