That’s probably the best idea. On Jun 29, 2010, at 4:34 PM, Jens Alfke wrote:
> > On Jun 29, 2010, at 12:11 PM, Dave DeLong wrote: > >> If you're spawning dozens of connections, you may want to consider giving >> each one a separate delegate object and encapsulating that connection's >> specific logic in that delegate. > > +1. I pretty much always make a class representing any sort of nontrivial use > of NSURLRequest. An instance of that class creates an NSURLRequest and makes > itself the delegate. Then when the callbacks arrive, all the necessary state > is easily available as instance variables. > > —Jens _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
