• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Tracking multiple NSURLConnections
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tracking multiple NSURLConnections


  • Subject: Re: Tracking multiple NSURLConnections
  • From: Scott Anguish <email@hidden>
  • Date: Tue, 29 Jun 2010 16:36:08 -0400

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@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

References: 
 >Re: Re: Tracking multiple NSURLConnections (From: email@hidden)
 >Re: Tracking multiple NSURLConnections (From: Dave DeLong <email@hidden>)
 >Re: Tracking multiple NSURLConnections (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: Tracking multiple NSURLConnections
  • Next by Date: Re: CoreData and undo/redo : how to add a managed object with attributes already set in the undo/redo stack ?
  • Previous by thread: Re: Tracking multiple NSURLConnections
  • Next by thread: Re: Tracking multiple NSURLConnections
  • Index(es):
    • Date
    • Thread