title: What major ASIHTTPRequest features is AFNetworking missing?
body: <p>With <a href="http://allseeing-i.com/%5Brequest_release%5D;" rel="nofollow noreferrer">work having recently stopped on ASIHTTPRequest</a>, it seems like attention is shifting to <a href="https://github.com/AFNetworking/AFNetworking" rel="nofollow noreferrer">AFNetworking</a>.</p>
  
  <p>However, I've not yet found a good comparison of the features of the two libraries, so I don't know what I might lose if/when I switch over.</p>
  
  <p>Major differences I've spotted so far are:</p>
  
  <ol>
  <li>AFNetworking has a much smaller code size (which is good)</li>
  <li>AFNetworking is being rapidly improved (so it may not yet be mature, may not have a stable API yet?)</li>
  <li>Both seem to have caching, though I've seen hints that because AFNetworking uses <a href="https://stackoverflow.com/questions/7166422/nsurlconnection-on-ios-doesnt-try-to-cache-objects-larger-than-50kb">NSURLConnection it won't cache objects over 50K</a></li>
  <li>ASIHTTPRequest has very good support for manual &amp; automatic (PAC) http proxies; I can't find any information on what level of support AFNetworking has for proxies</li>
  <li>AFNetworking requires iOS 4+, whereas ASIHTTPRequest works right back to iOS 2 (not really an issue for me, but it is an issue for some people)</li>
  <li>AFNetworking doesn't (yet) have a built in persistent cache, but there's a persistent cache which has a pending pull request: <a href="https://github.com/gowalla/AFNetworking/pull/25" rel="nofollow noreferrer">https://github.com/gowalla/AFNetworking/pull/25</a></li>
  </ol>
  
  <p>Has anyone seen any good comparisons of the two libraries or any documented experiences of switching from one to the other?</p>