views:

70

answers:

1

I have a lot of NSURLConnections downloading. They may not happen on the main thread. When some of them finish, I call performSelectorOnMainThread for a separate singleton object.

I've used both forms of performSelectorOnMainThread, specifying the run loop mode (NSDefaultRunLoopMode) and not specifying it. NSDefaultRunLoopMode is supposed to avoid NSConnection selectors, but the message still appears to be gated on them. The indicated selector is not performed until after all the pending connections have been completely downloaded.

How do I prioritize performSelectorOnMainThread to happen before the others?

A: 

Turns out I had another connection gating the one I had prioritized - performSelectorOnMainThread was not the problem.

shaheen