On 2010 Sep 23, at 02:21, Devraj Mukherjee wrote: > Previous version I used NSURLConnection to make synchronous calls to > the API, parsing the data and then returning results. Only problem of > course is that my API client had to be used in threads so the UI > didn't get locked up while the request was being made.
There are also the ill-defined errors that you get from sendSynchronousRequest:returningResponse:error:, which make it difficult to present appropriate error recovery. > I would like to move towards using async requests. Good idea. > I can grab / parse > the data using the delegate methods, what I am struggling with is how > I return the data to the application incorporating my library? > > Notifications? Or take define a protocol that the application has to > implement and call back appropriate messages? On 2010 Sep 23, at 05:37, Ken Thomases wrote: > You could follow the example of the class you're using. NSURLConnection uses > the delegate pattern. Indeed, there is the simple approach of having your data-consumer object create and own an NSURLConnection when needed, making itself the connection's delegate. Notifications, delegates, protocols will all work. The best approach may depend on other considerations in your app. _______________________________________________ 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
