Chapter 8: currentRunLoop vs mainRunLoop

Just curious, can anyone explain why setUpAsynchronousContentLoad messages currentRunLoop in [asyncInputStream scheduleRunLoop:[NSRunLoop currentRunLoop] forMode:NSDefaultRunLoopMode]; whereas, viewWillDisappear: messages mainRunLoop when removing the stream from the run loop? Without having seen this code, I would have either used currentRunLoop to schedule and remove or mainRunLoop for both. Is this a legacy issue or is there a specific NSStream logic to this discrepancy?

Hi Marc,

The stream was probably scheduled from the main loop so current == main.

Good luck!

A good thing I checked as I was going to post exactly that question Marc!

Bill (or whoever!) – two things:

) Why “probably”? (It’s page 152 in iPhone SDK Development, P1.0 printing)

) How would I know when they’re different?

Cheers.

Glad I checked here too, but I’m not seeing an explanation. :-( Yes, it’s evident that the cleanup is figuring it’s on the main run loop, but how is that assessment made? If you schedule an async and need to clean it up, is it always on the main? That seems odd. Why not use mainRunLoop in the schedule then? I’m concerned because if you do use “current run loop” in the viewWillDisapper, it crashes hard with and invalid selector.

Anyone figure this out in a deterministic way yet?