On 2010 Feb 09, at 14:10, Greg Reichow wrote: >> I'm trying to run an NSURLConnection from an NSOperation. Apparently, it >> won't run. I know that NSURLConnection need a run loop. Does that mean I'll >> have to setup some kind of NSTime in my NSOperation and then call my run >> loop at regular intervals? > > Try using the synchronous version of NSURLConnection since you are launching > it from within a NSOperation already- > > + (NSData *)sendSynchronousRequest:(NSURLRequest *)request > returningResponse:(NSURLResponse**)response error:(NSError **)error
Indeed sendSynchronousRequest: will work for a quick hack to talk to, say, your own server, but if you hope to some day have a real app which predictably handles real-world corner cases, well, let me quote what was told to me once: The NSErrors that you get from -sendSynchronousRequest: are not documented. For example, if you give it a wrong username/password combination, you get NSURLErrorUserCancelledAuthentication = -1012. Apparently this is an implementation detail, that when it receives an authentication challenge, it cancels. You're leaving the policy decisions to Apple instead of making them yourself, and since they are not documented, Apple may change them at any time. It is true that the alternative asynchronous methods require a run loop. (Don't use a timer). _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
