> On 30 Jul 2015, at 01:55, Rick Mann 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
> timeoutIntervalFor
On Fri, 31 Jul 2015 12:15:10 +0200, Jean-Daniel Dupas said:
>
>> Le 30 juil. 2015 à 18:26, Fritz Anderson a écrit :
>>
>> On 30 Jul 2015, at 11:03 AM, Trygve Inda wrote:
>>
>>> It seems Apple is using retain rather than copy for NSString properties in
>>> an NSManagedObject subclass.
>>>
>>>
> On 29 Jul 2015, at 15:35, Trygve Inda wrote:
>
>>
>> “Setter methods on queue-based managed object contexts are thread-safe. You
>> can invoke these methods directly on any thread”
>>
>> https://developer.apple.com/library/mac/documentation/Cocoa/Reference/CoreData
>> Framework/Classes/NSMan
> On Aug 1, 2015, at 06:02 , Mike Abdullah 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 bug, and
> worth
