|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
I wouldn't saw it's wrong, but separating logic definitely makes comprehension and implementation easier. Dave On Jun 29, 2010, at 1:23 PM, email@hidden wrote: > OK, makes sense. But is what I've done so wrong or is it just that there are better ways? > > > On Jun 29, 2010 2:11pm, Dave DeLong <email@hidden> 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. The url connection delegate might then have a weak pointer back to the original controller to notify when the connection is finished, at which point the controller could extract any data it needs from the connection delegate. > > > > > > > > Dave
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (email@hidden) 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: This email sent to email@hidden
|>Re: Re: Tracking multiple NSURLConnections (From: email@hidden)|
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.