On Oct 3, 2013, at 11:58 AM, Ken Thomases <[email protected]> wrote:
> That said, it's simple enough to write a category on NSThread such that you > can ask a thread to run a block and it will do so when its run loop is run. > Basically, it would leverage -[NSObject performSelector:onThread:…] and the > block would run in the same circumstances as a selector would. I’ve already got that and use it a lot in my code (see MYBlockUtils.m in MYUtilities.) > There is the question of why you want to dedicate a thread to running such > requests (and other run loop sources) rather than using the GCD worker > threads. Because I’ve got tens of thousands of lines of code*, a lot of which does some tricky asynchronous work using the runloop/thread paradigm, and I don’t want to break it by rewriting all of it en masse to use GCD. If I could start using GCD in new parts of the code that would be great, but when I tried to do so I ran into these impedance mismatches and had to tear it out. —Jens * https://github.com/couchbase/couchbase-lite-ios _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
