On 30 Jul 2015, at 01:55, Rick Mann rm...@latencyzero.com wrote:
I'm starting hundreds of download tasks on a single NSURLSession. The session
nicely limits the number of concurrent downloads, and everything seems to
behave, until I some time has elapsed equal to the default value of
On Aug 1, 2015, at 06:02 , Mike Abdullah mabdul...@karelia.com wrote:
When NSURLSession was first announced, I believe I enquired about this and
was told the timeout timer isn’t supposed to kick off until the task actually
does some work. That says to me the behaviour you’re seeing is a
On Jul 30, 2015, at 11:04 , Jens Alfke j...@mooseyard.com wrote:
On Jul 29, 2015, at 5:55 PM, Rick Mann rm...@latencyzero.com wrote:
It seems the only workaround is to make the timeoutIntervalForRequest very
long, too, which is gross, as a single request may legitimately time out in
On Jul 29, 2015, at 5:55 PM, Rick Mann rm...@latencyzero.com wrote:
It seems the only workaround is to make the timeoutIntervalForRequest very
long, too, which is gross, as a single request may legitimately time out in a
short amount of time, but the large set of tasks could take much
I'm starting hundreds of download tasks on a single NSURLSession. The session
nicely limits the number of concurrent downloads, and everything seems to
behave, until I some time has elapsed equal to the default value of
timeoutIntervalForRequest, 60 seconds (I don't currently adjust this).
