Re: NSURLSessionTasks don't have their own delegates?!
Re: NSURLSessionTasks don't have their own delegates?!
- Subject: Re: NSURLSessionTasks don't have their own delegates?!
- From: Shawn Erickson <email@hidden>
- Date: Tue, 22 Jul 2014 13:24:34 -0400
I am not implying anything close to that number.
If you have disjoint areas of code that need to execute tasks you can and in some situations likely should use a session instance dedicated to that area of things.
On Jul 22, 2014, at 1:09 PM, Jens Alfke < email@hidden> wrote: On Jul 22, 2014, at 9:28 AM, Shawn Erickson < email@hidden> wrote: I guess my point was that you don't need to confine yourself to a single global one, you can create multiple to divide up session behaviors for disjoint things.
I don’t think this is a good idea in general. For instance, each session has its own pool of TCP sockets per host*. So if I create 100 sessions (entirely possible if I’m creating a session per request) I may be opening 400 simultaneous sockets to the server, which could be bad.
—Jens
* Right? Because if not, that eliminates my main reason for switching to NSURLSession.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden