On Sat, Feb 14, 2009 at 11:42 PM, Jerry Krinock wrote:
>
> On 2009 Feb 14, at 08:36, Michael Ash wrote:
>
>> http://www.mikeash.com/?page=pyblog/dont-use-nsoperationqueue.html
>>
>> If you read all the way to the end you'll see that NSOperationQueue
>> can be induced to crash even when using only
On 2009 Feb 14, at 08:36, Michael Ash wrote:
http://www.mikeash.com/?page=pyblog/dont-use-nsoperationqueue.html
If you read all the way to the end you'll see that NSOperationQueue
can be induced to crash even when using only *one* queue in the entire
program, so you can't save yourself by shar
On Sat, Feb 14, 2009 at 1:49 AM, Jacob Rhoden wrote:
> Hi Guys,
>
> I have been starting to use NSOperationQueue. I have ended up with one put
> in each controller (ie see below), but now I have one in too many
> controllers. How does it work? Should I just have one global variable for
> the opera
hi Jacob,
Mike Ash has just posted blog entry on subject:
http://www.mikeash.com/?page=pyblog/friday-qa-2009-02-13-operations-based-parallelization.html
The answer depends on your code objectives,
Do you really need NSOperation instances and to queue them?
Maybe your task can be executed as single
Hi Guys,
I have been starting to use NSOperationQueue. I have ended up with one
put in each controller (ie see below), but now I have one in too many
controllers. How does it work? Should I just have one global variable
for the operation queue, or do multiple NSOperationQueue's "share" the
sa
