On Mon, Jul 21, 2014, at 08:03 PM, Jens Alfke wrote:
>
> On Jul 21, 2014, at 5:54 PM, Cody Garvin wrote:
>
> > I ended up writing a queue manager that took NSOperations along with times,
> > preflight block check and postflight block (setting other things up,
> > massaging, etc).
>
> Really,
> On 22 Jul 2014, at 8:42 am, Jens Alfke wrote:
>
> I’m starting to port a pretty complex source base from using NSURLConnection
> to using NSURLSession. (Primarily because this is the only way to get around
> the only-four-sockets-per-host limitation.) I thought it was going to be
> straight
I'd love to be wrong. Hopefully I am.
Please excuse mobile typos
> On Jul 21, 2014, at 6:03 PM, Jens Alfke wrote:
>
>
>> On Jul 21, 2014, at 5:54 PM, Cody Garvin wrote:
>>
>> I ended up writing a queue manager that took NSOperations along with times,
>> preflight block check and postflight
On Jul 21, 2014, at 5:54 PM, Cody Garvin wrote:
> I ended up writing a queue manager that took NSOperations along with times,
> preflight block check and postflight block (setting other things up,
> massaging, etc).
Really, we have to reinvent NSTimer ourselves? Especially after Apple optimiz
I know it’s not NSOperationQueue but GCD has dispatch_after.
I ended up writing a queue manager that took NSOperations along with times,
preflight block check and postflight block (setting other things up, massaging,
etc).
I don’t thinkw NSOperationQueue has an equivalent. Could be wrong
- Co
I’m starting to port a pretty complex source base from using NSURLConnection to
using NSURLSession. (Primarily because this is the only way to get around the
only-four-sockets-per-host limitation.) I thought it was going to be
straightforward, until I saw that NSURLSession only supports scheduli
