Re: Re: Tracking multiple NSURLConnections
Re: Re: Tracking multiple NSURLConnections
- Subject: Re: Re: Tracking multiple NSURLConnections
- From: email@hidden
- Date: Tue, 29 Jun 2010 19:23:34 +0000
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
On Jun 29, 2010, at 1:08 PM, email@hidden wrote:
> Now, a devil's advocate question:
> If I have lots of connections, say two dozen, or say I'm spawning
connections continuously, would this be the most efficient way of doing
this? I'd likely store them in an NSArray and iterate/compare until I
find the right one. There could be lots of comparisons.
_______________________________________________
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