> On Nov 23, 2016, at 8:16 AM, Shawn Erickson <shaw...@gmail.com> wrote: > > We throttle for 3 main reasons. 1) Starting many requests - in our experience > - results in a far higher likelihood of requests randomly timing out. It > seems like the timeout starts ticking relative to creation of the task - > possibly initial resume - and not after some internal throttling takes place. > That makes firing off a large number of requests a little to non > deterministic.
I’ve run into the same problem, and also use throttling to avoid it. (However, this was several years ago; I would hope this would have been fixed by now. Pretty sure I filed a Radar at the time.) To be precise: the behavior I saw is that if you set a timeout on an NSURLRequest, start the request, and if after that interval the request hasn’t actually been sent over the wire yet, the request will fail with a timeout error. If you queue up requests faster than the session can send them, this is a real problem. —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to arch...@mail-archive.com
