setting limit on concurrent tasks in AFNetworking 2 running AFHTTPSessionManager

余生颓废 提交于 2019-11-28 17:58:57

AFHTTPSessionManager uses tasks instead of operations (NSURLSessionDataTask, specifically), which is why you can't set an operation queue.

As you can see in the implementation of this class, tasks are immediately started ([task resume]) and not added to any sort of queue.

Consequently, and unfortunately, there is no built-into-AFNetworking way to set a limit to the number of concurrent tasks using AFHTTPSessionManager.

Possible alternatives:

  1. Use AFHTTPRequestOperationManager instead (this is what I'm doing)
  2. Build an NSOperation subclass that has a task as a property, and start the task in the [operation start] method of your subclass
  3. Create a Grand Central serial queue and create and start tasks in this queue
  4. If your requests are all to the same host, directly access the HTTPMaximumConnectionsPerHost option in the foundation URL loading system, like so:

    [NSURLSessionConfiguration defaultSessionConfiguration].HTTPMaximumConnectionsPerHost = 4;
    

    This approach has a number of caveats, which are discussed in the Apple documentation.

If you wind up doing #2, please submit it as a pull request to AFNetworking - it would be a welcome addition.

You can configure AFHTTPSessionManager NSURLSessionConfiguration:

NSURLSessionConfiguration *config = [NSURLSessionConfiguration defaultSessionConfiguration];
config.HTTPMaximumConnectionsPerHost = 2;

AFHTTPSessionManager *manager = [[AFHTTPSessionManager alloc] initWithSessionConfiguration:config];
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!